-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Don't silently process.exit #12042
Comments
Hmm I have no idea why that's there. And yeah, it doesn't make any sense. Luckily my almost ready to go PR just removed that file. |
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
We should move to process.exitCode instead. I think it's a good idea to handle this inside gatsbyjs/rfcs#31 |
Oh this is fixed now. |
The linked file doesn't exist anymore |
Calling
process.exit
without an error message is really hard to debug.The text was updated successfully, but these errors were encountered: