Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wrong sourceMappingURL

See original GitHub issue

sourceMappingURL is wrongly relative to scss file, should be relative to css file instead.

$ bin/sassc --version
sassc 0.12.3 (sass/libsass 3.4.3)
$ mkdir -p scss target/css
$ touch scss/style.scss
$ sassc -g scss/style.scss target/css/style.css
$ cat target/css/style.css
/*# sourceMappingURL=../target/css/style.css.map */

If browser tries to access ../target/css/style.css.map from target/css/style.css, it would get 404 on target/target/css/style.css.map.

Doesn’t seem like C libsass’s issue.

Issue Analytics

State:
Created 6 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

bachewcommented, Oct 4, 2017

Thanks, it works now.

0reactions

asottilecommented, Jun 8, 2017

This is now part of 0.13.0 \o/

Top Results From Across the Web

Incorrect sourceMappingURL path · Issue #146 - GitHub

The sourceURL seems fine with and without source-map-loader . The decoded sourceMappingURL incorrect though once this loader is added to an ...

Warning: -file- is being assigned a //# sourceMappingURL, but ...

The JavaScript warning "-file- is being assigned a //# sourceMappingURL, but already has one." occurs when a source map has been specified more...

4 Reasons Why Your Source Maps are Broken - Sentry Blog

Missing or incorrect source map directive · Missing original source files · Bad source maps caused by multiple transformations · Files are ...

JavaScript Debugging with Sourcemaps - TrackJS

Enter the Sourcemap. A sourcemap is a mapping between the generated/transpiled/minified JavaScript file ... TrackJS Error Report TrackJS Sourcemap Applied ...

Angular source maps sourceMappingUrl broken

I have recently upgraded from Angular 7 to Angular 8 and I noticed that in Chrome and Firefox I have an error ......