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.

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

[breaking] require Node 16.9 #5395

Merged
merged 1 commit into from
Jul 7, 2022
Merged

[breaking] require Node 16.9 #5395

merged 1 commit into from
Jul 7, 2022

Conversation

benmccann
Copy link
Member

closes #5370

not exactly sure why Node 16.9 is now required, but it fixes it, so 🤷

@changeset-bot
Copy link

changeset-bot bot commented Jul 6, 2022

🦋 Changeset detected

Latest commit: 4fdfbf2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@sveltejs/kit Patch

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

@Rich-Harris
Copy link
Member

I was hoping to figure out why it's failing with 16.7 before resorting to this (though bumping the required version isn't the end of the world, since it's unlikely someone would be forced to be on 16.7)

@Rich-Harris
Copy link
Member

It turns out that undici requires 16.9 because it uses things like util.toUSVString (introduced in 16.8) and Object.hasOwn (introduced in 16.9), even though its engines field incorrectly says otherwise (nodejs/undici#1526 (comment)).

I think that's unlikely to change, so I'll merge this

@Rich-Harris Rich-Harris merged commit 7c9f720 into master Jul 7, 2022
@Rich-Harris Rich-Harris deleted the node-16.9 branch July 7, 2022 20:49
This was referenced Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid request body
2 participants