Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger scans whole forlder for source maps when sourceMaps option is false. #866

Closed
Megabyteceer opened this issue Nov 26, 2020 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@Megabyteceer
Copy link

Describe the bug
I don use js generation and have project with a lot of .js code. At debugging start browser freezes for a minute, and processMonitor shows that vscode scans js files. Documentation says that outFiles option used only if sourcrMaps is enabled. Adding empty pattern in to outFiles solves the problem, but it is not very obvious. Maybe if vscode have no find any sourcemaps ask user to disable scanning?

VS Code Version: 1.51.1

Additional context

@Megabyteceer Megabyteceer added the bug Issue identified by VS Code Team member as probable bug label Nov 26, 2020
@connor4312 connor4312 added this to the November 2020 milestone Nov 26, 2020
@Megabyteceer
Copy link
Author

That was fast. Thank you : )

@roblourens roblourens added the verified Verification succeeded label Dec 2, 2020
@syvuilliot
Copy link

the option "sourceMaps: false" seems to be ignored again, since I need to configure "outFiles: []" to disable sourceMaps scanning to prevent very long startup of debugger in a js only repo

This is true since vscode 1.69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants