Chrome intercept points jump to different lines

I run Chrome 48.0, and recently, when I try to place breakpoints in the developer's console, sometimes they refuse to be placed in certain lines and instead go to another line. In much the same way, when you try to place a breakpoint on a line that doesn't make sense (like a bracket in itself), but these are regular lines. If I make changes to my code, the lines that refuse to work may change, and the lines that worked before that may stop working.

I suppose this has something to do with source matching, but I'm confused why some lines are working correctly and there won't be a line right after that.

I use grunt-browsify with babelify and babel-preset-react, babel-preset-es2015 and babel-plugin-syntax-object-rest-spread:

options: { transform: [['babelify', { presets: ['react', 'es2015'], plugins: ['syntax-object-rest-spread'], }]], browserifyOptions: { extensions: ['.jsx'], paths: [absPath + '/js', absPath], debug: true // Adds source maps to output }, 

Any idea what could happen?

+7
javascript google-chrome gruntjs source-maps grunt-browserify
source share

No one has answered this question yet.

See related questions:

4086
What is the difference between using "let" and "var"?
2984
What is the difference between calling and applying?
2237
How to pass command line arguments to Node.js?
1700
What is the difference between Bower and npm?
1554
Disabling Chrome Web Site Cache
1403
Disable same origin policy in Chrome
593
How to set JavaScript breakpoint from code in Chrome?
3
Using babel-polyfill with grunt and browser
0
Compose an isomorphic answer with Babelify & Grunt
0
Module assembly failed (from. / Node_modules / babel-loader / lib / index.js)

All Articles