Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[bug] unknown reason debug process start twice #17

Open
bluelovers opened this issue Aug 23, 2020 · 7 comments
Open

[bug] unknown reason debug process start twice #17

bluelovers opened this issue Aug 23, 2020 · 7 comments
Labels
3rd-party

Comments

@bluelovers
Copy link
Owner

currently this bug only happen for me

#14 (comment)

#14 (comment)

#14 (comment)
@bluelovers
Copy link
Owner Author

bug is by esm-ts-node

@Garethp
Copy link
Contributor

Garethp commented Aug 24, 2020

How do you reproduce this? How to use esm-ts-node? Re-open this ticket, I'll try to help

@bluelovers
Copy link
Owner Author

image

bluelovers added a commit to bluelovers/ws-esm-ts-node that referenced this issue Aug 24, 2020
@bluelovers
fix: bluelovers/idea-run-typescript#17
41590cd
@Garethp
Copy link
Contributor

Garethp commented Aug 24, 2020

Only run once for me, but debug not working

@Garethp
Copy link
Contributor

Garethp commented Aug 24, 2020

I know what's wrong. Getting debug message twice is correct with esm-ts-node. Only runs once, but debug connects twice.

  1. Debug connects to main process
  2. esm-ts-node creates a child process
  3. Debug connects to child process.

One run, two messages

@bluelovers bluelovers reopened this Aug 24, 2020
@bluelovers
Copy link
Owner Author

looks like can't fix this by delete NODE_OPTIONS lol, it will make debug point not work

@bluelovers bluelovers reopened this Aug 24, 2020
@Garethp
Copy link
Contributor

Garethp commented Aug 24, 2020

How about not using esm-ts-node? When you have debug with esm-ts-node selected, you can instead run node -r esm -r ts-node/register directly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3rd-party
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bluelovers @Garethp