-
-
Notifications
You must be signed in to change notification settings - Fork 808
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
fix: process.kill("SIGABRT") not supported on windows #4308
Conversation
🦋 Changeset detectedLatest commit: 26e104d The changes in this PR will be included in the next version bump. This PR includes changesets to release 8 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
e457d68
to
df295ae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @lmisea thanks for the PR! LGTM!
Can you run pnpm changeset
and set the type to patch
for blitz
in the root directory to create the changeset explaining this change (it will be included in the release)
Added @lmisea contributions for doc and code |
Closes: #4307
What are the changes and their implications?
process.kill("SIGINT")
instead ofprocess.kill("SIGABRT")
onstartCustomServer()
at next-utils.ts on blitz package.process.kill("SIGABRT")
is not supported on Windows.Bug Checklist
pnpm changeset
in the root directory) (patch bump)Feature Checklist
pnpm changeset
in the root directory)main
branch)