Skip to content
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

Add a temporary workaround to get building on Node 18 since Node 16 EOL is 2023-09-11 #6053

Closed
wants to merge 1 commit into from

Conversation

tsmock
Copy link
Contributor

@tsmock tsmock commented Sep 8, 2023

This does the following:

  • Add NODE_OPTIONS=--openssl-legacy-provider (not needed once we upgrade to react-scripts v5 or remove/replace react-scripts)
  • Only adds NODE_OPTIONS when run on node 18 or later
  • Performs frontend-code-test on node 18
  • Does not run backend_deploy/frontend_deploy with node 18. This can be changed via using cimg/python:3.10-node (versions after 3.10.8-node use node 18 instead of node 16)

Node 16 EOL Notice: https://nodejs.org/en/blog/announcements/nodejs16-eol
create-react-app --openssl-legacy-provider: facebook/create-react-app#11562

This is intended to be a temporary fix for #5767.

…OL is 2023-09-11

This does the following:
* Add NODE_OPTIONS=--openssl-legacy-provider (not needed once we upgrade
  to react-scripts v5 or remove/replace react-scripts)
* Only adds NODE_OPTIONS when run on node 18 or later
* Performs frontend-code-test on node 18
* Does _not_ run backend_deploy/frontend_deploy with node 18. This can
  be changed via using cimg/python:3.10-node (versions after 3.10.8-node
  use node 18 instead of node 16)

Node 16 EOL Notice: https://nodejs.org/en/blog/announcements/nodejs16-eol
create-react-app --openssl-legacy-provider: facebook/create-react-app#11562

Signed-off-by: Taylor Smock <[email protected]>
@sonarcloud
Copy link

sonarcloud bot commented Sep 8, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.2% 0.2% Duplication

@dakotabenjamin
Copy link
Member

We built some node images for this issue while we work to get TM running on a newer version: https://quay.io/repository/hotosm/node?tab=tags

@ramyaragupathy
Copy link
Member

@varun2948 @tsmock - with the node upgrade coming from #5721 merge is this relevant?

cc @royallsilwallz @manjitapandey

@tsmock
Copy link
Contributor Author

tsmock commented May 1, 2024

Nope. We can close this.

@tsmock tsmock closed this May 1, 2024
@tsmock tsmock deleted the chore/nodejs18 branch May 1, 2024 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants