Invalid sourcemaps on v3.0.0
See original GitHub issueHey just a heads up, when I tried upgrading to 3.0.0 I was getting source map errors when trying to load the sourcemaps again downstream.
Example:
return gulp.src([
rootDir + '/styles/sass/*.scss'
])
.pipe(sourcemaps.init())
.pipe(sass().on('error', sass.logError))
.pipe(sourcemaps.write('./'))
.pipe(gulpif(minifyMe, cssMin()))
.pipe(gulp.dest(sassifiedDir));
Then trying to call sourcemaps.init({loadMaps: true}) elsewhere throws:
Error: Invalid mapping: {"generated":{"line":8370,"column":7},"source":"app/vendors/bower_components/robo-ui/dist/sass/mixins/_clearfix.scss","original":{"line":3,"column":-38},"name":null}
I downgraded to 2.3.2 and it works now, but wanted to let you know.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:18
- Comments:28
Top Results From Across the Web
Webpack is producing invalid sourcemaps? #8302 - GitHub
My hypothesis is that the orig_map (which has been essentially passed through to terser from webpack) has incorrect mappings (the "non-minified ...
Read more >reactjs - Incorrect source maps - Stack Overflow
The solution was passing the code to compilers in the correct order: First babel-loader , then ts-loader . Had to change my webpack...
Read more >API - esbuild
#Sources content. Supported by: Transform | Build. Source maps are generated using version 3 of the source map format, which is by far...
Read more >Source Map Revision 3 Proposal
Line 3: An optional name of the generated code that this source map is ... “null” may be used if some original sources...
Read more >source-map-explorer - npm
The source map explorer determines which file each byte in your minified code came from. It shows you a treemap visualization to help...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There’s already a patch https://github.com/sass/libsass/pull/2540 and should be part of the next libsass release.
Looks like it fixed in v3.2.0