purescript / purescript/npm-installer
Check node version manually on startup
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
The purescript npm package currently has an engines constraint of >= 10.16.0, but this does not appear to be sufficient to stop people getting confused when the installer fails on older node versions, see e.g. https://github.com/purescript/purescript/issues/3677. I think this is because npm only warns on an unsatisfied engines constraint by default rather than erroring.
We can make these failures easier to understand (and also not reliant on details of the particular npm client in use) by checking for them manually in this package and generating the appropriate errors ourselves.
Contributor guide
No contributing guide indexed for this repository
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 inspecting the purescript npm package's startup path and its existing engines constraint of >= 10.16.0, then review the failure context in issue 3677. Done means older Node versions receive clear errors from the package itself rather than relying on npm's warning behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100