Problems with Chrome debugging in dev with webpack
See original GitHub issueBy default, the generated webpack.dev.conf.js
sets devtool: '#cheap-module-eval-source-map'
. This causes problems with Chrome debugging because of https://github.com/vuejs/vue-cli/issues/51. Changing devtool
in the generated webpack.dev.conf.js
to #source-map
solves the issue. Is there any way to control the devtool
setting from index.js
? I see that for production webpack config it is set to config.build.productionSourceMap ? '#source-map' : false
.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Webpack not accessible in Chrome debugger - Stack Overflow
I open the Chrome development tools, click on the "sources" tab, navigate my way to the "Webpack" link on the left, and find...
Read more >How to debug a webpack app in the browser - Jakob Lind
What you need to do now is to open the developer tools in Chrome. Either right-click on your page and select “inspect element”...
Read more >Debugging | webpack
As most front-end developers already know, Chrome DevTools are a life saver when debugging web applications, but they don't have to stop there....
Read more >Webpack Source Mapping for Debugging in Chrome
Using source maps solves this problem by allowing you to debug the ... In Google Chrome, open DevTools by clicking command + option...
Read more >Learn and Debug webpack with Chrome Dev Tools! - Medium
You can also help diagnose build time problems by running the javascript profiler seen here: Using the profiler from Chrome Dev Tools (left)....
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 Free
Top 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
I also faced issues while trying to debug in chrome with
#cheap-module-eval-source-map
. I was able to fix it by changing it back to#eval-source-map
.@LinusBorg understood. Hopefully it’ll get resolved upstream in webpack. Thanks for the reply!