[104] Adds node and npm versions to package.json and .node-version file #116
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.
Description
Issue #104.
Adds node and npm versions to the engines property in
package.json
so developers know which versions of node are supported. Also adds a.node-version
file so package managers automatically use the recommended version.I set the recommended node version to 18 as it still has a year left in it's lifecycle. I didn't go with node version 20 as some of our installed dependencies do not support it in their current versions. See screenshot:
Change Log
.node-version
file to set the default node version to 18.Steps to test
fnm
as your package manager, the node version should automatically switch to version 18.node_modules
folder.npm i
.npm watch:dev
and check that the plugin still works.Checklist: