oxidecomputer / oxidecomputer/cockroach
update node runtime
Open
Nobody has claimed this yet.
derisking
- Dominant language
- Go
- Stars
- 34
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
@puppeteer/browsers is complaining:
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@puppeteer/browsers@3.0.5',
npm WARN EBADENGINE required: { node: '>=22.12.0' },
npm WARN EBADENGINE current: { node: 'v20.11.1', npm: '10.2.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'yargs@18.0.0',
npm WARN EBADENGINE required: { node: '^20.19.0 || ^22.12.0 || >=23' },
npm WARN EBADENGINE current: { node: 'v20.11.1', npm: '10.2.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'yargs-parser@22.0.0',
npm WARN EBADENGINE required: { node: '^20.19.0 || ^22.12.0 || >=23' },
npm WARN EBADENGINE current: { node: 'v20.11.1', npm: '10.2.4' }
npm WARN EBADENGINE }
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or target version is named. Locate the repository's Node/npm runtime declaration, then reproduce the install warnings with the current setup and compare the required engine versions shown in the issue. Done means the declared runtime satisfies the listed package requirements and the warnings no longer occur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100