Node warnings with more readable Node versions #410
Merged
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
Feedback from sprint demo:
The node version range is now taken from the engines field of the package.json, which is more readable than seeing semver's representation (>=12.0.0 <13.0.0-0||>=14.0.0 <15.0.0-0).
Follow up to this merged PR #384
Types of Changes
How to Test-Drive This PR
First of all, run
npm ci
at the root of the monorepo to rebuild all the packages.Then try testing the generator:
nvm use 13
node packages/pwa-kit-create-app/scripts/create-mobify-app-dev.js --outputDir /tmp/project
... Your app may not work as expected when deployed to Managed Runtime servers which are compatible with Node ^12.0.0 || ^14.0.0
Also, try running the dev server from within the 'pwa' package:
npm start
And try running
npm ci
at the root folder too with an incompatible node version.Checklists
General
Accessibility Compliance
You must check off all items in one of the follow two lists:
or...
Localization