chore: Upgrade to Node v20 #1968
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@elliot is attempting to deploy a commit to the shadcn-pro Team on Vercel. A member of the Team first needs to authorize it. |
|
@shadcn CI issue with |
|
I was just searching for popular repositories which still use end-of-life Node.js versions, and came across this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Node v16 ended support on 11 Sep 2023.
This PR
.nvmrcfrom 16 to 20actions/checkoutfrom v3 to v4actions/setup-nodefrom v2 to v4pnpmdependencies, simplifying the workflowpnpmversion constraintNote
There is a warning for
TypeError: The "code" argument must be of type number. Received an instance of Objectwhich will be fixed in the PR below. It does not appear to affect typechecking