mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Blake Friedman
4410899ec7
Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/45544 ## This diff now does 5 things: 1. removes the old way we used `actions/setup-node` to manage the cache itself. 2. it creates a new `update-node-modules-cache` workflow, which is the only job that will update the node modules cache 3. it create a `yarn-install-with-cache` action that should be used install of directly calling `yarn install --non-interactive`. This will load a cache against a hash of `package.json`. 4. updated the cache reaper to aggressively remove everything but the latest `npm-{{ hash('package.json') }}`. 5. removed a `cache-setup`, which couldn't be used (we're using artefacts now). ## Why are we doing this: The various `node-cache-` keys for platforms and on various branches accounts for a very large proportion of the cache (10-20%). We don't frequently change these dependencies, and even when we do running `yarn install` after loading the cache will resolve any issues. Limiting the cache to `main` and aggressively pruning older cache entries will clean up a lot of "small win" caching. Changelog: [Internal] Reviewed By: cortinico Differential Revision: D59917944 fbshipit-source-id: 4be6f1959e8fde642a4f208f7d19aceba2c3262f
15 lines
371 B
YAML
15 lines
371 B
YAML
name: Setup node.js
|
|
description: 'Set up your GitHub Actions workflow with a specific version of node.js'
|
|
inputs:
|
|
node-version:
|
|
description: 'The node.js version to use'
|
|
required: false
|
|
default: '18'
|
|
runs:
|
|
using: "composite"
|
|
steps:
|
|
- name: Setup node.js
|
|
uses: actions/setup-node@v4
|
|
with:
|
|
node-version: ${{ inputs.node-version }}
|