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
and is not an entrypoint to rollup (like a private component in src/-private/foo.gjs that is imported and used internally)
then rollup would
move that component module around (component is in /dist/foo-<randomnumbers>.js)
leave the CSS in place (/dist/-private/foo.css)
and not rewrite the import (still import './foo.css';)
so webpack (in the consuming app) would expectedly throw an error.
It can be worked around by making all modules entrypoints (like addon.publicEntrypoints(['**/*.js'])). Addons could still limit the public/importable modules through package.json#exports.
Not sure if that's something we should move to?
The text was updated successfully, but these errors were encountered:
When modules reference static assets added to the build via the `keepAssets` rollup plugin, and those modules are not entrypoints and as such moved into a bundle at a different location, the relative path to that asset would not get rewritten, leading to broken references.
Fixesembroider-build/addon-blueprint#192
When you have a component that
import './foo.css';
src/-private/foo.gjs
that is imported and used internally)then rollup would
/dist/foo-<randomnumbers>.js
)/dist/-private/foo.css
)import './foo.css';
)so webpack (in the consuming app) would expectedly throw an error.
It can be worked around by making all modules entrypoints (like
addon.publicEntrypoints(['**/*.js'])
). Addons could still limit the public/importable modules throughpackage.json#exports
.Not sure if that's something we should move to?
The text was updated successfully, but these errors were encountered: