Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Website migration steps for Nodejs 16

See original GitHub issue

I 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 then nvm 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 GitHub Comments

4reactions

svengabrcommented, Feb 4, 2022

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.

1reaction

MikeMcC399commented, Feb 4, 2022

@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.)

I also submitted a related PR for the documentation repository. https://github.com/corona-warn-app/cwa-documentation/pull/844. Perhaps somebody could take a look at this one as well. The documentation PR is not so critical because 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.