You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
The existing Node debugger only binds breakpoints in source if their sourcemaps can be found from outDir/outFiles ahead of time, but there are some scenarios where sourcemaps can't be resolved ahead of time, or don't exist on disk.
To handle this, the adapter needs to hold on to unbound bp info, and when a script is loaded and new sourcemaps are resolved, it needs to bind those bps and send BreakpointEvents informing the frontend that the bps are now bound.
There are a few relevant scenarios in Node like with SystemJS and Babel dynamic require, but it's more important in browser scenarios where we can't resolve URL -> script until the script is loaded (without adding yet another config parameter). Used to work in Chrome until I started using configurationRequest, so I hope to create the full fix soon.
The text was updated successfully, but these errors were encountered:
The existing Node debugger only binds breakpoints in source if their sourcemaps can be found from outDir/outFiles ahead of time, but there are some scenarios where sourcemaps can't be resolved ahead of time, or don't exist on disk.
To handle this, the adapter needs to hold on to unbound bp info, and when a script is loaded and new sourcemaps are resolved, it needs to bind those bps and send BreakpointEvents informing the frontend that the bps are now bound.
There are a few relevant scenarios in Node like with SystemJS and Babel dynamic require, but it's more important in browser scenarios where we can't resolve URL -> script until the script is loaded (without adding yet another config parameter). Used to work in Chrome until I started using configurationRequest, so I hope to create the full fix soon.
The text was updated successfully, but these errors were encountered: