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 Feb 8, 2024. It is now read-only.
Unfortunately, I wasn't able to find a workaround on how to reliably attach debugger to a process running through @swc/register.
Sourcemaps are fine when building the project with the same configuration and debugging the compiled js file. However, that's a large inconvenience for an interactive debugging of large node projects.
// EDIT: I've just tried with https://github.com/swc-project/swc-node and it's working correctly. Should that @swc-node/register be used instead of @swc/register?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've been digging into details while preparing reproduction for the following IntelliJ issue: https://youtrack.jetbrains.com/issue/WEB-52287/Debugging-doesnt-work-correctly-with-swc-transpiler-https-github.com-swc-project-swc
It looks like the source maps are not outputted, or incorrect in some way? See the attached issue, and the reproduction repository: https://github.com/wodCZ/swc-register-inspect-repro
Unfortunately, I wasn't able to find a workaround on how to reliably attach debugger to a process running through
@swc/register
.Sourcemaps are fine when building the project with the same configuration and debugging the compiled js file. However, that's a large inconvenience for an interactive debugging of large node projects.
// EDIT: I've just tried with https://github.com/swc-project/swc-node and it's working correctly. Should that
@swc-node/register
be used instead of@swc/register
?The text was updated successfully, but these errors were encountered: