Website migration steps for Nodejs 16
See original GitHub issueI migrated a copy of the cwa-website to Nodejs 16 and I successfully tested it. I can provide more details if desired.
The currently used Nodejs version 14 is supported for another 16 months until end of Apr 2023, however there might be other reasons to migrate, apart from this end-of-life date.
Steps to migrate
- Update working environment
nvm install lts/gallium
and thennvm use lts/gallium
(Node v16) - Modify build workflow to use Node v16
- Modify deploy-master workflow to use Node v16
Workaround for Panini
Building the web causes the error:
Error: Panini: rendering error occured.
RangeError: Maximum call stack size exceeded
Removing the 5.5 MB interactive graph (“Fig. 6: EDUS participants by 3-digit postcode and district.”) from each language version of the Science 2 blog prevents this error occurring.
Edit: Removed the following steps which have now been completed through PR https://github.com/corona-warn-app/cwa-website/pull/2178.
- Install node-sass@6 through npm (previously using version 4)
- Install gulp-sass@5 through npm (previously using version 4)
- Modify gulpfile.js to use gulp-sass@5
Internal Tracking ID: EXPOSUREAPP-10928
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Migrate to Node.js 16 - Auth0
Enable Node 16 on your development tenant using the Extensibility panel on the Advanced Tenant Settings page of the Dashboard. · Click Save....
Read more >Everything about the latest Node.js release | Node.js 16
Summary of the major changes: · Node.js v16. · Experimental implementation of the standard Web Crypto API · Abort controller: It's was an ......
Read more >Guides - Node.js
Getting Started Guide · Debugging - Getting Started · Easy profiling for Node.js Applications · Diagnostics - Flame Graphs · Dockerizing a Node.js...
Read more >How to migrate Nodejs from v4.5 to v12 Step by Step
How to migrate Nodejs from v4.5 to v12: Step by Step Instal of a later version of nodejs on a linux (ubuntu) Amazon...
Read more >How to upgrade Node.js and dependencies. Results.
This is a how-to article reflecting back on our upgrade process from Node.js 8 to Node.js 12 for the Snugg Pro web application....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The pull request was finally merged today. Thank you very much for your contribution @MikeMcC399 !
I did also close the internal Jira Issue
EXPOSUREAPP-10928
. If you have any issues with the new version, please open a new issue.@svengabr
I’m happy that this was able to be merged! I agree that any resulting questions / problems are better covered in new issue(s).
Thanks also from me for your trust! (I know you tested as well of course.)
node
/npm
are only used for CI checking. There is no website build which could be affected like here. The idea is just to keep the repositories on the same level, so that contributors do not have to switch versions to stay compatible.