question-mark
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.

Issue with sourcemaps (later transformations)

See original GitHub issue

Please refer to https://github.com/floridoo/gulp-sourcemaps/issues/124.

I am experiencing exactly the same problem using the following Gulp task (ES2015):

gulp.task("build-css", () => {
    return gulp.src(cssSrc)
        .pipe(newer({
            dest: cssDest,
            ext: ".css"
        }))
        .pipe(sourcemaps.init({debug: true}))
        .pipe(sass({
            // See: https://github.com/sass/node-sass/issues/957
            //outputStyle: "compressed"
            outputStyle: "expanded"
        }).on("error", sass.logError))
        .pipe(autoprefixer({
            // Default for Browserslist (https://github.com/ai/browserslist) @ 2015/09/18
            browsers: ["> 1%", "last 2 versions", "Firefox ESR"]
        }))
        .pipe(sourcemaps.write(".", {debug: true}))
        .pipe(gulp.dest(cssDest));
});

Could it be the same thing described in this comment?

Versions:

  • OS: Windows 7 (x64)
  • Node: 4.1.1
  • NPM: 3.3.4
  • gulp-sourcemaps@1.6.0
  • gulp-sass@2.1.0-beta
  • gulp-autoprefixer@3.0.2

Issue Analytics

  • State:open
  • Created 8 years ago
  • Comments:21 (4 by maintainers)

github_iconTop GitHub Comments

5reactions
glen-84commented, Dec 11, 2015

@xzyfer I don’t understand. I took the time to create a very simple repo that clearly shows the issue (see this comment).

@clee704 and @backflip have also supplied test cases, and @backflip has even specified what breaks and in which versions it breaks.

What else could you need? 😕

2reactions
xzyfercommented, Dec 11, 2015

Unfortunately no one has submitted a test case showing exactly what sass is required to break source maps. We know there are issue but source maps complicated and with very specific test cases there isn’t much we can do. On 11 Dec 2015 9:10 pm, “Glen” notifications@github.com wrote:

@xzyfer https://github.com/xzyfer Now that LibSass 3.3.0 has shipped, when do you think that you might have time to look into this?

— Reply to this email directly or view it on GitHub https://github.com/dlmanning/gulp-sass/issues/354#issuecomment-163898753 .

Read more comments on GitHub >

github_iconTop Results From Across the Web

4 Reasons Why Your Source Maps are Broken - Sentry Blog
Bad source maps caused by multiple transformations​​ That's because the source map only converts from the minified (Uglified) code back to the ...
Read more >
Sourcemap transformation issue with Browserify > Exorcist ...
The problem: my build pipeline is broken, most likely the sourcemap transformations (webpack > browserify > exorcist > sorcery) through various ...
Read more >
Source Maps | webpack surviveJS - GitHub Pages
When your source code has gone through transformations, debugging becomes a problem. When debugging in a browser, how to tell where the original...
Read more >
508270 - Source maps cache not refreshed - chromium
What is the expected result? Source maps should not be cached. Changes in a transpiled JS file + its according source map should...
Read more >
Transformer - Parcel
The source code or content of the asset can be retrieved, along with any associated source map (see below). The transformer can then...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found