setup-node
setup-node copied to clipboard
actions
Set up your GitHub Actions workflow with a specific version of node.js
[Stylelint](https://stylelint.io/) has a [`compact` formatter](https://stylelint.io/user-guide/cli#--formatter--f) that is (nearly) compatible with ESLint one's. It outputs lowercase severity strings though, so [`eslint-compact` matcher](https://github.com/actions/setup-node/blob/v1.3.0/.github/eslint-compact.json)'s RegExp is not triggered. This PR changes the matcher...
**Description:** It would be nice to be able to [configure npm](https://docs.npmjs.com/cli/v7/using-npm/config#ignore-scripts) to ignore pre and postinstall scripts. **Justification:** Pre/postinstall scripts are a potential security problem. **Are you willing to submit...
**Description:** Since Node.js 19, the default for `keepAlive` was changed from `false` to `true`. As explained in [this similar issue for the Ruby setup action](https://github.com/ruby/setup-ruby/issues/543#issuecomment-1793608370), this causes the Post setup...
**Description:** I've upgraded minor version of @actions/cache in order to solve the issue "Intermittently, the setup-node action times out after 60 minutes. Logs indicate that it's restoring yarn cache" **Related...
**Description:** Initializes cache variable closer to usage **Related issue:** Discovered while going through the source code **Check list:** - [ ] Mark if documentation changes are required. - [ ]...
**Description:** After reviewing the [source code](https://github.com/actions/setup-node/blob/main/src/main.ts#L36-L52), it appears that providing an empty string to the `node-version` input is the simplest approach to bypassing Node.js installation, which may require greater explanation...
**Description:** actions/setup-node does not support Azure DevOps Artifacts even though DevOps is also a Microsoft product. This is because `actions/setup-node` configures a temporary `.npmrc` file with an `_authToken` syntax, but...
**Description:** It would be nice to have the option to restore only and not save. **Justification:** In bigger repos, it's easy to hit the 10gb cache limit. Not caching in...
Is there a way to setup the action to use npm 7? What about `npm_version: 7` like actually it's done for `node_version`?
### Description Currently the behavior is that `node-version` is preferred rather than `node-version-file` if both are provided. https://github.com/actions/setup-node/blob/d86ebcd40b3cb50b156bfa44dd277faf38282d12/src/main.ts#L85-L95 I would like to propose the opposite since `node-version` is actually hardcoded...
