You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2020. It is now read-only.
I used devtool: 'source-map' in webpack config and did not use babili-webpack-plugin.
Here are some code of my source file:
var b = 1024;
console.log(10)
All worked great, I could set breakpoint to line: var b = 1024;
and to line console.log(10)
Also I could see the value of "b" variable during debugging.
But after I added babili-webpack-plugin I can not see the value of "b" variable. Also now I can set breakpoint only to line: console.log(10)
and can not set breakpoint to line: var b = 1024;
Is it an issue or maybe I do something wrong? Here is part of my webpack.config.js
I have the same kind of issues except that I barely see any source maps at all once I activate the babili plugin... Is it possible that there is an incompatibility between the Babili plugin and ExtractTextPlugin, or handlebars-loader ?
I used devtool: 'source-map' in webpack config and did not use babili-webpack-plugin.
Here are some code of my source file:
All worked great, I could set breakpoint to line:
var b = 1024;
and to line
console.log(10)
Also I could see the value of "b" variable during debugging.
But after I added babili-webpack-plugin I can not see the value of "b" variable. Also now I can set breakpoint only to line:
console.log(10)
and can not set breakpoint to line:
var b = 1024;
Is it an issue or maybe I do something wrong? Here is part of my webpack.config.js
The text was updated successfully, but these errors were encountered: