Support `.node-version`/`.nvmrc` file
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 140
- Forks
- 19
- Avg merge
- 13h 19m
- Merged PRs (30d)
- 3
Description
The actions/setup-node action supports a node-version-file input, which can point to a file that contains the version of node.js to use. It would be great if this action could also support reading the runtime version from a file (other than package.json).
We use a .node-version file to automatically get the correct Node.js version based on folder, using nvs auto. There is a PR to add that support, and if that was merged, I'd be happy for package.json to be the source of truth for the Node.js version instead, but until that point, I'd love if I could keep using .node-version without duplicating that version elsewhere in the codebase.
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
The issue identifies package.json as the current source and the action's runtime-version input as the entry point. Read that handling first, then trace how a version-file option could accept .node-version and .nvmrc; done means either file supplies the Node.js version without duplicating it in package.json, with existing behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100