This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 119
Enable source maps by default to simplify configuration #134
Comments
Thoughts on this @weinand? It shouldn't break anyone since you can turn on 'sourceMaps' then debug your code without sourcemaps just fine. |
If this change affects node2, then we will have to flip the defaults in node1 as well. |
Right, it should be consistent across. We can change it in chrome-debug to experiment. |
Let's ship this in the Chrome debugger, and evaluate the results. |
roblourens
added a commit
to microsoft/vscode-chrome-debug
that referenced
this issue
Jan 2, 2017
Enabled for chrome-debug in 2.4.2! |
Yay. Let's see how people are gonna react to this. |
56 tasks
This was referenced Jan 20, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: