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 you use the --sourcemap argument in the CLI to generate the CSS builds with sourcemaps, when the CSS uses @include, it does not update the path and therefore will not work.
In the code below, the builds are stored in the dist directory, while the CSS source code is stored in the src directory.
Lightning CSS does not rewrite import paths. But perhaps you could consider using --bundle to combine all of your source files into a single output file?
These are the scripts in my package.json to bundle the CSS. When I add the --bundle flag to the dev script, the source maps wil not work but when I remove the --bundle flag, it will work but with broken sourcemaps as described in the original post.
When you use the
--sourcemap
argument in the CLI to generate the CSS builds with sourcemaps, when the CSS uses@include
, it does not update the path and therefore will not work.In the code below, the builds are stored in the dist directory, while the CSS source code is stored in the src directory.
This is my simple code to reproduce this...
bundle.css
demo.html
package.json
src/stylesheet.css
dist/my-package.css output
What I expected from the dist/my-package.css output
The text was updated successfully, but these errors were encountered: