-
Notifications
You must be signed in to change notification settings - Fork 64
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
build: upgrade to node16 #259
Conversation
9dfe35f
to
847d145
Compare
Codecov Report
@@ Coverage Diff @@
## master #259 +/- ##
=======================================
Coverage 80.79% 80.79%
=======================================
Files 38 38
Lines 885 885
Branches 163 163
=======================================
Hits 715 715
Misses 159 159
Partials 11 11 Continue to review full report at Codecov.
|
@@ -6,34 +6,37 @@ on: | |||
- master | |||
pull_request: | |||
branches: | |||
- '**' |
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.
my editor / vscode reformatted this file if this is not acceptable, I can revert! I have to check what settings exist that are doing this
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.
This shouldn't be an issue. If this is the only change, then you can merge with this change since both versions are syntactically correct.
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.
FWIW, I don't think the "**" is needed here. Just having pull_request
under on
should suffice to get the workflow to run on all Paragon PR updates.
Actually there is an issue! With new node version, start fails like this
|
5985263
to
3cab0e2
Compare
Description:
Was awaiting #245 so now this is unblocked
locally: Devs should ideally use
nvm use
after syncing repo, clean out node modules andnpm ci
: nvm automatically chooses latest node/npm version for v16 based on .nvmrc filein Github builds: tooling is configured to honor .nvmrc already
Alternative to use nvm is to manually install node16/npm8 but note that different projects may be (as of now) using different node versions, so nvm is highly recommended
Description:
Upgrades project to use nvmrc and node16 (specified in nvmrc file)
Local dev users should either:
NOTE: since nvmrc uses the
v16
version, nvm will choose the latest node and npm versions under the major version (v16.y.z for node and v8.y.z for npm) applicable when you runnvm use
Describe what this pull request changes, and why. Include implications for people using this change.
Merge checklist:
frontend-platform
. This can be done by runningnpm start
and opening http://localhost:8080.module.config.js
file infrontend-build
.fix
,feat
) and is appropriate for your code change. Consider whether your code is a breaking change, and modify your commit accordingly.Post merge: