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
When debugging a nodejs application via the VS Code debugger, when you hit a breakpoint, the debugger will take you to a readonly source mapped file.
This is terribly un ergonomic since you must then manually navigate to the source file before you can make any changes.
This only started happening from the upgrade of rules_typescript=0.10.1 to current.
While the old issue of having source maps point to a symlinked file was also a unergonomic way to handle it, this is even worse and a blocker for us upgrading.
The ideal situation would be for source maps to point back to the source file
The text was updated successfully, but these errors were encountered:
When debugging a nodejs application via the VS Code debugger, when you hit a breakpoint, the debugger will take you to a readonly source mapped file.
This is terribly un ergonomic since you must then manually navigate to the source file before you can make any changes.
I believe this now superseeds bazelbuild/rules_typescript#254
This only started happening from the upgrade of rules_typescript=0.10.1 to current.
While the old issue of having source maps point to a symlinked file was also a unergonomic way to handle it, this is even worse and a blocker for us upgrading.
The ideal situation would be for source maps to point back to the source file
The text was updated successfully, but these errors were encountered: