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
{{ message }}
This repository was archived by the owner on Aug 4, 2021. It is now read-only.
@Rich-Harris mentioned this already in #2 (comment) that named imports/exports are really difficult or even completely unfeasible.
The problem is that the current pattern is extremely popular, and established tools (even rollup) work well with it.
So far I use rollup with external to link to npm modules and it works like expected with named imports. Switching to rollup-plugin-commonjs however breaks because it now complains about missing exports (since the converted modules only have a default export and nothing else).
@Rich-Harris mentioned this already in #2 (comment) that named imports/exports are really difficult or even completely unfeasible.
The problem is that the current pattern is extremely popular, and established tools (even rollup) work well with it.
So far I use rollup with
externalto link to npm modules and it works like expected with named imports. Switching to rollup-plugin-commonjs however breaks because it now complains about missing exports (since the converted modules only have a default export and nothing else).