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

deps: use node20 and npm 11 #223

Merged
merged 1 commit into from
Jan 15, 2025
Merged

Conversation

v1v
Copy link
Member

@v1v v1v commented Jan 14, 2025

npm 11 stopped support for node18

See https://github.com/npm/cli/releases/tag/v11.0.0

npm now supports node ^20.17.0 || >=22.9.0

Therefore, the CI stopped working. See https://github.com/elastic/opbeans-frontend/actions/runs/12727194854/job/35476446434?pr=221

> [3/7] RUN npm install npm@latest -g:
0.783 npm error code EBADENGINE
0.783 npm error engine Unsupported engine
0.783 npm error engine Not compatible with your version of node/npm: [email protected]
0.783 npm error notsup Not compatible with your version of node/npm: [email protected]
0.783 npm error notsup Required: {"node":"^20.17.0 || >=22.9.0"}
0.783 npm error notsup Actual:   {"npm":"10.8.2","node":"v18.20.5"}
0.7[86](https://github.com/elastic/opbeans-frontend/actions/runs/12727194854/job/35476446434?pr=221#step:3:87) npm error A complete log of this run can be found in: /root/.npm/_logs/2025-01-11T20_03_25_637Z-debug-0.log
------
Dockerfile:11

npm 11 stopped support for node18
@v1v v1v requested a review from kuisathaverat January 14, 2025 14:17
@v1v v1v self-assigned this Jan 14, 2025
@v1v v1v merged commit 2ed7a9e into elastic:main Jan 15, 2025
3 checks passed
@v1v v1v deleted the feature/pin-versions-npm branch January 15, 2025 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants