This repository was archived by the owner on Oct 2, 2021. It is now read-only.
This repository was archived by the owner on Oct 2, 2021. It is now read-only.
Enable source maps by default to simplify configuration #134
Closed
Description
Given the popularity of sourcemaps we should flip our default setting, so sourcemap support are enabled by default.
Rational:
If a source map is present it's most likely needed to resolve paths correctly. Some people don't notice the sourcemap
config, and end up with a bad first time experience.
We should therefore flip the setting, and explicitly allow people to disable source maps if needed.
This would simplify the default configs too.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
roblourens commentedon Dec 5, 2016
Thoughts on this @weinand? It shouldn't break anyone since you can turn on 'sourceMaps' then debug your code without sourcemaps just fine.
weinand commentedon Dec 5, 2016
If this change affects node2, then we will have to flip the defaults in node1 as well.
I will investigate what consequences this has in the January milestone.
roblourens commentedon Dec 5, 2016
Right, it should be consistent across. We can change it in chrome-debug to experiment.
auchenberg commentedon Dec 6, 2016
Let's ship this in the Chrome debugger, and evaluate the results.
Enable sourceMaps by default for microsoft/vscode-chrome-debug-core#134
roblourens commentedon Jan 2, 2017
Enabled for chrome-debug in 2.4.2!
auchenberg commentedon Jan 3, 2017
Yay. Let's see how people are gonna react to this.