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

Usage of NodeJS 18 LTS #2295

Closed
1 task done
etec-masterofsynapse opened this issue Nov 6, 2022 · 6 comments
Closed
1 task done

Usage of NodeJS 18 LTS #2295

etec-masterofsynapse opened this issue Nov 6, 2022 · 6 comments
Labels
area:core issues describing changes to the core of uptime kuma feature-request Request for new features to be added

Comments

@etec-masterofsynapse
Copy link

etec-masterofsynapse commented Nov 6, 2022

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

The install guide for non-Docker installs in the wiki recommends NodeJS 14 or higher, but the easy install script installs 14 when using the non-Docker way.
NodeJS 14 LTS will be End-of-Maintenance in April 2023, not that far off.
Are there major headaches to be expected when using NodeJS 18 LTS today?

✔️ Solution

Usage of NodeJS 18 LTS

❓ Alternatives

No response

📝 Additional Context

No response

@etec-masterofsynapse etec-masterofsynapse added the feature-request Request for new features to be added label Nov 6, 2022
@louislam
Copy link
Owner

Uptime Kuma should be working fine on Node.js 18, you can update your Node.js manually.

@etec-masterofsynapse
Copy link
Author

Uptime Kuma should be working fine on Node.js 18, you can update your Node.js manually.

In that case, are there plans to refresh the install script to use 18 going forward?

@RalfSoft
Copy link

Node18 would be great. And if you update install scripts / docker containers, please consider using the user node and not root inside the container! (Security)

@christopherpickering
Copy link
Contributor

If you get the error:0308010C:digital envelope routines::unsupported on website running on an old IIS+.net with node 18, I found that running NODE_OPTIONS=--openssl-legacy-provider pm2 restart uptime-kuma --update-env fixes the error.

@CommanderStorm
Copy link
Collaborator

@RalfSoft

And if you update install scripts / docker containers, please consider using the user node and not root inside the container! (Security)

This is one of the features slated for the v2 release.
See #2720

@CommanderStorm CommanderStorm added the area:core issues describing changes to the core of uptime kuma label Dec 8, 2023
@CommanderStorm
Copy link
Collaborator

Installation script has been sunset and node 14 is tracked in #3746
=> closing as resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core issues describing changes to the core of uptime kuma feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

5 participants