Skip to content

fix: eval webpack config breakpoints not setting #1833

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

Merged
merged 3 commits into from
Oct 6, 2023

Conversation

connor4312
Copy link
Member

V8 does not resolve URL-set breakpoints when the script in question only
has that URL via a sourceURL mapping.

I also noticed an issue with per-script entrypoint breakpoints where
another file with the same name, or part of the same name, could
incorrectly remove the entrypoint breakpoint early. It's fine to just
leave the breakpoint around -- can be slightly slower, but better than
missing the breakpoint entirely.

Fixes microsoft/vscode#194988

V8 does not resolve URL-set breakpoints when the script in question only
has that URL via a sourceURL mapping.

I also noticed an issue with per-script entrypoint breakpoints where
another file with the same name, or part of the same name, could
incorrectly remove the entrypoint breakpoint early. It's fine to just
leave the breakpoint around -- can be slightly slower, but better than
missing the breakpoint entirely.

Fixes microsoft/vscode#194988
@connor4312 connor4312 enabled auto-merge (squash) October 6, 2023 17:31
@connor4312 connor4312 disabled auto-merge October 6, 2023 17:43
lramos15
lramos15 previously approved these changes Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Breakpoints not binding on typescript project on one machine
3 participants