source-maps

I am struggling to get my SASS sourcemaps to work correctly. The problem seems to be the "sources" attribute within the sourcemap and how my SASS files are nested. I have a Gulp task that compiles SASS to CSS. Here is an example of that var paths = { styles: { src: './Stylesheets/SCSS/', files: './Stylesheets/SCSS/**/*.scss', dest: './Stylesheets/CSS/' } } gulp.task('compile-sass', function (){ return gulp.src(paths.styles.files) .pipe(sourcemaps.init()) .pipe(sass({ outputStyle: 'compressed', includePaths : [paths.styles.src] })) .pipe(prefix({ browsers: ['last 2 Chrome versions'], cascade:

I am not able to load sourcemap in Chrome Extension for some reason. The folder which is being loaded for Chrome Extension has .map just next to .js file. With the .js file having the line //# sourceMappingURL=1.9215106f1980d05d2b4c.js.map referencing the .map file path. However, the Chrome dev-tools is not loading the maps for some reason. I double checked the Chrome settings to make sure that the js source maps is turned on and it is working with a simple Angular project. Also, made sure I have the following in the manifest file: "web_accessible_resources":[ "*.map" ], 来源： https:/

My current webpack.config file module.exports = { entry: "./entry.js", output: { devtoolLineToLine: true, sourceMapFilename: "./bundle.js.map", pathinfo: true, path: __dirname, filename: "bundle.js" }, module: { loaders: [ { test: /\.css$/, loader: "style!css" } ] }, }; I was reading here https://webpack.github.io/docs/configuration.html and found the following: output.sourceMapFilename [file] is replaced by the filename of the JavaScript file. [id] is replaced by the id of the chunk. [hash] is replaced by the hash of the compilation. I've added it above as you can see, but when my webpack

Within Google Chrome, I was wondering if stack traces will, in the future, provide mapping support. Currently, using source maps, throwing an error will provide the line number link to my TypeScript files, however... When calling the Error.stack, it gives me the JavaScript lines and files. Here's a reference picture: http://puu.sh/4DTOG.png As you'll notice, the actual line the error is on is linked to the TypeScript file, but the stack trace links to the JavaScript files. There is no inherent technical limitation. However I don't think it is planned. For reasons like, when the stack trace

It looks as though LESS debugging has come a decent distance since even a year ago, and I was wondering how many people have experience with debugging using developer tools in Chrome/Canary. I'm trying to ensure that when I'm debugging a file, the element's CSS shows up as the LESS file, rather than the CSS file. It's of little use to have CSS line numbers show up, when I need to know the requisite line number of the LESS file. I can do this in firefox with firebug and fireless, but it's not working in chrome I tried to follow the steps here , however it doesn't appear to be functioning for me

I decided to try out WebPack on a new project I'm spinning up today and I'm getting really strange behavior from the sourcemaps. I can't find anything about it in the documentation, nor can I find anyone else having this issue when skimming StackOverflow. I'm currently looking at the HelloWorld app produced by Vue-CLI's WebPack template -- no changes have been made to the code, the build environment, or anything. I installed everything and ran it like so: vue init webpack test && cd test && npm install && npm run dev Looking at my sourcemaps, I see the following: This is a hot mess. Why are