Use #cheap-module-eval-source-map for development

[CodinCat]

The build speed of cheap-module-eval-source-map is faster than just eval-source-map, and it works very well in most scenarios.

Thus I'd recommend to use cheap-module-eval-source-map for development.

webpack docs: https://webpack.github.io/docs/configuration.html#devtool

[maxmilton]

Seams to work as expected in my project setups :)

[myst729]

I personally use #source-map. It's only slow at the initial build.

eval-source-map is fast (honestly I didn't feel it) but I found it cannot debug JS in *.vue via Chrome DevTools.

[mdartic]

I agree with @myst729, I use only #source-map, because it allows me to debug in Firefox.

Chrome seems working well with both eval-source-map and cheap-module-eval-source-map.

@yyx990803 could we imagine that in the cli there is a prompt to ask the user which strategy he wants to use ?

[myst729]

@mdartic

Well, I don't think it's a good idea. The interactive wizard should focus the high level decisions. Let the detailed configurations stay in the files for manual adjustment. Otherwise the wizard will inevitably turn into a pain.

[mdartic]

Yep, I understand.

[yoyo837]

Please keep the following comments：cheap-module-eval-source-map is faster for development, but chrome doesn't stop at breakpoints.