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
We cannot do them for both. In the current best case scenario would be doing this:
"exports": {"./string": "./dist/string.js"// for external packages"./src/string": "./dist/string.js"// for internal packages},
However, given our effort to remove barrel imports, having two export paths for every export gets unwieldy very fast (see types package).
This issue is for doing research on how to improve this situation that is the most maintainable possible. Idea: perhaps at build time for external packages, the package.json fields can be overwritten programatically.
The text was updated successfully, but these errors were encountered:
(Given #672 is merged)
Removing barrel files makes imports look like this:
External apps that import our package from NPM could do this:
Internal packages that would want the same thing would have to do this:
We cannot do them for both. In the current best case scenario would be doing this:
However, given our effort to remove barrel imports, having two export paths for every export gets unwieldy very fast (see types package).
This issue is for doing research on how to improve this situation that is the most maintainable possible. Idea: perhaps at build time for external packages, the package.json fields can be overwritten programatically.
The text was updated successfully, but these errors were encountered: