source-maps

So far, debugging in GWT super dev mode seems to be a real pain. If there are any errors, there is no stack trace, just a cryptic message given in the chrome console. Is there a way to get all errors to print a stack trace, like in the dev mode? I already have source maps on I believe, since if I go to Sources in Chrome's dev tools, I can see the source code of my java classes. Click Upvote GWT.setUncaughtExceptionHandler lets you set an exception handler, which will handle all exceptions. You can then get the stacktrace of that exception using something like this code , and then print

I have an es6 project which I bundle using webpack + babel loader. When I open the devtools I can see 'webpack://' and all my sources (es6) underneath. The problems are: breakpoints don't hit and function references directs me to a file name '?d41d which has the following content: undefined /** WEBPACK FOOTER ** ** **/ if I drill down from document script to a function in my bundle I get to the ?d41d file as well my webpack.config.js: module.exports = { debug: true, devtool: 'cheap-module-eval-source-map', entry: "entry.js", output: { path: "C:/html5/", filename: "bundle.js" }, module: {

I'm pretty new to webpack and having some trouble configuring it to produce the necessary source maps. In the devtools it says Source Map detected but it shows the bundle and not the original code: Here is my webpack.config.js: module.exports = { entry: [ 'webpack-dev-server/client?http://localhost:8080/', 'webpack/hot/dev-server', "./src/index.js" ], output: { filename: 'bundle.js', path: '/', }, debug: true, devtool: 'source-map', resolve: { extensions: ['', '.jsx', '.scss', '.js', '.json'] }, module: { loaders: [ { test: /(\.js|\.jsx)$/, exclude: /node_modules/, loaders: ['react-hot','babel

I want to debug a node app that runs from babel compiled ES6 files. I have my ES6 source in an src folder and the babel ES5 equivalent in a build folder. Project root | | build | > ES5 Compiled files | | src | > ES6 Source files My goal: Place breakpoints directly in my ES6 source. I have generated proper source maps and I made a node debug configuration that runs the ES5 main file with project root set as working directory. I can break when I set breakpoints in ES5 compiled files, and it automatically shows my ES6 source. However I'd like to place breakpoints directly in the ES6 source . Is

I have created a concatenated, minified file through the Node.js wrapper for Google Closure Compiler . When I open the Developer Tools in Google Chrome, both the source map and the mapped files all load appropriately. A problem I'm having is that breakpoints aren't triggering in the source map files like they would running an unminified, separate-file session. Sometimes I'll try to place a breakpoint in a script and it will jump several lines down rather than where I'm trying to set it. But what is most frustrating is that when I can set a breakpoint, they aren't triggered! I'll set one in the

Visual Studio 2013 UP5 + Web Essential's (v. 2.6.36) generated css.map files are invalid in "Google Chrome", however it is valid in "Firefox". Due to this it became impossible to debug less files in google chrome. Currently, I am using Web Essential 2.6.36 (+ Visual Studio 2013 Up5). I can disable the source map from google chrome's developer's setting. Which will remove those errors, however still we cannot debug less files and change the style. Which is a terrible problem. Any advice will be appreciated. Thank you in advance. PeterMacko Problem is that WebEssentials saves files in UTF8 with

Apart from enabling source maps in Chrome, in my gulpfile.js I use errLogToConsole: true, sourceComments: 'map', sourceMap: 'sass' as arguments when calling sass based on this answer : gulp.task('sass', function() { return gulp.src('../assets/styles/**/*.scss') .pipe(plumber({ errorHandler: onError })) .pipe(sass({errLogToConsole: true, sourceComments: 'map', sourceMap: 'sass'})) .pipe(autoprefixer()) .pipe(gulp.dest('../dist/styles')) .pipe(browserSync.reload({ stream: true })) }); Yet SCSS content still doesn't show up in DevTools. Why? Note: source map comments do show up in compiled CSS as