-
-
Notifications
You must be signed in to change notification settings - Fork 536
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
Support --inspect #218
Comments
That was fast, thanks! :-) I did a quick test to verify like this: test1.ts
I then open the provided debug URL in chrome within 20 seconds and can see the test1.ts file in the tree. I set a breakpoint on the goodbye line and it hits. So far it works great. However for me the sourcemaps don't get loaded correctly. When I open the |
I'm happy to keep the discussion here, just because I have no idea how to fix that. It seems like I'd be going into the Chrome debugger territory. Does babel's source maps work? Is there possibly some flag or config you need to change to use the source map? The source maps definitely work in |
Actually, see nodejs/node#8369 perhaps? |
Yes, it looks to me as ts-node is providing all that should be needed so that nodejs issue is probably what is causing it. I will subscribe to that and see what they come up with. Thanks again for adding the option. |
I just tried debugging vitest test in chrome however I get |
try this: |
node options need to be passed to node, not to ts-node. There are a few options for this. One is using |
It is possible to run
node --inspect test1.js
and get a link to debug in chrome. See here.Would it be possible to add support for
ts-node --inspect test1.ts
and get similar support?Seems babel-node has support for this.
The text was updated successfully, but these errors were encountered: