You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we dont add new dependencies to the exclude list in rollup config, then the dependency will be bundled. This is in most cases not what we want - we want the dependency to be resolved automatically where the package is used.
Could also look into if there exists a rollup plugin to handle this automatically, similar to how peerDependencies are handled
Tasks
No response
Acceptance Criterias
Document that when adding a new dependency to package.json, you also have to update exclude list in rollup config
OR
Find a plugin that will deal with this automatically
The end result should be the same - items in dependencies in package.json should not be part of the generated bundle.
The text was updated successfully, but these errors were encountered:
haakemon
added
status/draft
Status: When you create an issue before you have enough info to properly describe the issue.
and removed
status/draft
Status: When you create an issue before you have enough info to properly describe the issue.
labels
Jul 7, 2022
Description
If we dont add new dependencies to the
exclude
list in rollup config, then the dependency will be bundled. This is in most cases not what we want - we want the dependency to be resolved automatically where the package is used.Related comment #60 (comment)
Additional Information
Could also look into if there exists a rollup plugin to handle this automatically, similar to how peerDependencies are handled
Tasks
No response
Acceptance Criterias
OR
The end result should be the same - items in
dependencies
in package.json should not be part of the generated bundle.The text was updated successfully, but these errors were encountered: