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
As the modules and packages grows, it is becoming increasingly complex to manage imports and exports. Bundling all exports into one index.js file for small modules make senses but for large more complex modules it is harder to effectively manage conflicts. E.g. jellyfish-api-core, hence it is wise to implement subpath exports vs named exports for larger packages.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
Custom subpaths can be defined along with the main entry point by treating the main entry point as the "." subpath:
This allow loading a sub path
Why is this needed:
As the modules and packages grows, it is becoming increasingly complex to manage imports and exports. Bundling all exports into one
index.js
file for small modules make senses but for large more complex modules it is harder to effectively manage conflicts. E.g.jellyfish-api-core
, hence it is wise to implement subpath exports vs named exports for larger packages.The text was updated successfully, but these errors were encountered: