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
When using * in front of the package name to make all dependencies external the kind of packages that are split will also seemingly consider their own internal modules external. This means the import map in browsers will need to include the internal package name with weird letters in the map.
Edit: This issue may overlap (or even be a duplicate of) #925 - at least the resulting problem is the same:
It is really hard to know ahead-of-time what the "internal externals" are going to be named because the names are not in any package.json and they include seemingly random letters. So far we have been just letting the import fail, note the name and manually added them to the import map.
The text was updated successfully, but these errors were encountered:
When using * in front of the package name to make all dependencies external the kind of packages that are split will also seemingly consider their own internal modules external. This means the import map in browsers will need to include the internal package name with weird letters in the map.
Is this intentional?
For example @monogrid/gainmap
https://esm.sh/*@monogrid/gainmap-js@3.1.0/es2022/gainmap-js.mjs (this depends on @monogrid/gainmap-js/dist/QuadRenderer-DuOPRGA4)
https://esm.sh/@monogrid/gainmap-js@3.1.0/es2022/gainmap-js.mjs (this depends on ./dist/QuadRenderer-DuOPRGA4.mjs)
Also @use-gesture/core
https://esm.sh/*@use-gesture/core@10.3.1/es2022/core.mjs (this depends on @use-gesture/core/dist/actions-fe213e88.esm which in turn depends on @use-gesture/core@10.3.1/es2022/dist/maths-0ab39ae9.esm.mjs)
https://esm.sh/@use-gesture/core@10.3.1/es2022/core.mjs (this depends on relative module ./dist/actions-fe213e88.esm.mjs which in turn depends on relative module ./maths-0ab39ae9.esm.mjs)
Edit: This issue may overlap (or even be a duplicate of) #925 - at least the resulting problem is the same:
It is really hard to know ahead-of-time what the "internal externals" are going to be named because the names are not in any package.json and they include seemingly random letters. So far we have been just letting the import fail, note the name and manually added them to the import map.
The text was updated successfully, but these errors were encountered: