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
Endo supports importing arbitrary modules from packages that do not supply "exports" in their package.json. To ensure that a package that works in development will also work after publication, Endo should fail if a module is absent from files.
The text was updated successfully, but these errors were encountered:
I would like to punt or possibly even just not do this for modules. The qualifiers for modules are already sufficiently limited (they must have a .js, .cjs, .mjs, or .json extension), the behaviors of npm-packlist are sufficiently complex and so deeply entwined with fs (via glob), that a faithful emulation might be more trouble than it’s worth.
The story for respecting files for non-module resources may be a good place to revisit this issue.
Endo supports importing arbitrary modules from packages that do not supply
"exports"
in theirpackage.json
. To ensure that a package that works in development will also work after publication, Endo should fail if a module is absent fromfiles
.The text was updated successfully, but these errors were encountered: