Skip to content
This repository was archived by the owner on Dec 19, 2025. It is now read-only.

Conversation

@zanemcca
Copy link

@zanemcca zanemcca commented Aug 3, 2022

I ran into the issues described in #69 and I found that none of the proposed solutions were working for me.

In order to reproduce the issue I made sure to trigger a change in my node_modules before my application had fully started up. This seemed to always result in the SIGTERM being swallowed by some other listener instead of properly shutting down the application. This results in ts-node-dev perpetually hanging.

The solution here is to simply send a SIGINT after a preset delay if the SIGTERM does not result in the application exiting on it's own.

@m-abboud
Copy link

m-abboud commented Oct 9, 2022

This has definitely fixed the issue for us where it wouldn't restart if you made changes too quickly, thank you 🙇‍♀️

@zanemcca
Copy link
Author

@wclr could we get this bad boy merged in and deployed by any chance?

@sunsama sunsama closed this by deleting the head repository Feb 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants