CodeKit icon indicating copy to clipboard operation
CodeKit copied to clipboard

CSS Sourcemaps missing sources after update to build 34704

Open AforDesign opened this issue 8 months ago • 2 comments

I've noticed that sourcemaps are not created correctly anymore after updating to the latest build (34704). The Codekit build I used before the update was 34680.

To make sure none of my own settings made a difference, I restored an older commit in my GIT repo which still had the working sourcemap and then recompiled my .scss file.

Here's a copy of the beginning of my css.map file, compiled with both build 34680 and build 34704

Compiled with build 34680: {"version":3,"sources":["wsw.css","../scss/originals/reset.css","<no source>","../scss/originals/base.css","../scss/originals/style.css","../scss/layout/_general.scss","../scss/layout/_content.scss","../scss/components/_background-panels.scss","../scss/components/_buttons_main.scss","../scss/components/_footer.scss","../scss/components/_tweets.scss"],"names":[],"mappings":".......

Compiled with build 34704: {"version":3,"sourceRoot":null,"mappings":"":".......

As you can see, the 'sources' property is empty, the 'names' property removed and a new 'sourceRoot' property with value null is set.

AforDesign avatar Jun 04 '25 10:06 AforDesign

I'm not able to reproduce this over here. The test projects I use show source maps generating correctly. Can you send me a small demo project that shows the issue? Zip the whole thing and send me a download.

bdkjones avatar Jun 04 '25 22:06 bdkjones

After a short break, my head cleared up a bit and I thought of what might caused the problem I ran into. It occurs when 'Minify the output' is turned on.

AforDesign avatar Jul 09 '25 07:07 AforDesign