-
Notifications
You must be signed in to change notification settings - Fork 69
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
Match the Node version in nvm with the minimum version in package.json #9190
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.33 MB ℹ️ View Unchanged
|
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.
Looks good!
I had this problem the other day. Was thinking to create a PR with exactly the same change (my locally installed node was also 20.11) but decided not to because the readme clearly states to run |
@shendy-a8c Interesting. Thanks for highlighting this tidbit. I always start with |
#9190) Co-authored-by: Shendy <73803630+shendy-a8c@users.noreply.github.com>
Changes proposed in this Pull Request
Node version in our plugin was recently upgraded from 16 to 20 in #9121. nvm was configured to use any v20 release. This is out of sync with the minimum version specified in
package.json
- 20.11 - which may cause issues for someone with 20 < v < 20.11 installed. This PR brings the nvm version in sync with the one in package.json.Testing instructions
Without this change:
nvm use
. This will pick up your local v20 installation.npm install
. It will fail saying you do not need the minimum node version.With this change:
nvm use
. You will be prompted to install a newer node version. Go ahead with it.npm install
will succeed.npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge