mitcoding

As a temp fix so that I could use the transform directly out of lightingcss I used the type option in a hacky way to disable further processing of the...

I just uploaded the bundle files that cause the issue. with that said the specific merge I'm asking for that sorcery does that esbuild doesn't do, which you can see...

i've uploaded an example project that repoduces the issue described above. the final files generated by esbuild are in target/clientlib-site1/site1.EXT and the pre-minified files generated by esbuild-sass-plugin and lightiningcss are...

I have seen this same issue made worse when minifing so I've disabled minify so that source maps work better. I had meant to open a ticket just like this...

@rgpublic I only mentioned Esbuild as that is how I stumbled on a similar issue (if not the exact same one) as yours. To Clarify, when I also use lightingcss...

@rgpublic Ok looking at your unminified css file, what sticks out to me is lines 224-232 which happens to be above ".paragraph-stage .body .field-body h1.text-align-center strong" (which is line 316)...

@rgpublic ok I missed the index.scss only saw index.css. With that said using the CLI for dart-sass and lightniningcss: sass --embed-sources --embed-source-map index.scss test_unminified.css; lightningcss --bundle -m --sourcemap -o test.css...

@rgpublic My bundler uses a script like yours as well which I linked to above https://github.com/mitcoding/esbuild-sass-source-map-issue. I just wanted to show that I could reproduce the issue with the CLI,...