Request: support node version from .tool-versions file
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 140
- Forks
- 19
- Avg merge
- 13h 19m
- Merged PRs (30d)
- 3
Description
We are currently using asdf to manage our node.js and ruby runtimes, which are specified in a .tool-versions file, and have a fair bit of tooling built which references this file. I'd like to swap over from corepack and actions/setup-node, but ideally without having to specify my node.js version in package.json. The node action allows:
with:
node-version-file: ".tool-versions"
Would you consider something like this, to support such a file? (or .node-version or .nvmc for those using such files)
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 reading the action’s existing runtime-version input handling and the setup-node/corepack path referenced in the issue. Compare the requested .tool-versions, .node-version, and .nvmc formats with current behavior; done means the action can obtain the Node.js version from a supported file without requiring package.json.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100