Dependency on specific npm Version
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 138
- Forks
- 26
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 3
Description
Hey everyone,
We're trying to use this package in our project, but the installation fails:
```
/app $ npm install @mapbox/assembly
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: @mapbox/assembly@1.5.1
npm ERR! notsup Not compatible with your version of node/npm: @mapbox/assembly@1.5.1
npm ERR! notsup Required: {"node":">=14","npm":"^6.0.0"}
npm ERR! notsup Actual: {"npm":"9.4.0","node":"v19.6.0"}
```
Is there a reason for **limiting the usable npm version** in such a way?
(Even if that is necessary for development, it might not be for projects using this library?)
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
Start by locating the package metadata that declares the Node and npm engine requirements shown in the report. Check those declarations against the reported Node 19 and npm 9 installation, and verify that installation no longer produces the EBADENGINE error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100