actions/setup-node
actions/setup-node
3
0
Fork 0
mirror of https://gitea.com/actions/setup-node.git synced 2024-11-25 03:29:33 +01:00
Code Issues Projects Activity Pipelines

Update 0000-caching-dependencies.md

Browse source
This commit is contained in:
Maxim Lobanov 2021-05-26 17:27:14 +03:00
parent 5fddb2d510
commit ae26aaf1b5
1 changed files with 0 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
docs/adrs/0000-caching-dependencies.md
View file

@ -26,7 +26,6 @@ We don't persue the goal to provide wide customization of caching in scope of `a
- Add optional input `package-lock-path` that will allow to specify path to `package-lock.json` file path:
- If input is not defined, action will try to search `package-lock.json` or `yarn.lock` (npm 7.x supports `yarn.lock` files) files in the repository root and throw error if no one is found
- If input contains file path, action will use the specified file
- If input contains folder path, action will try to search `package-lock.json` file in the specified folder
- if input contains wildcards (like `**/package-lock.json`), hash of multiple files will be used
- The hash of file provided in `package-lock-path` input will be used as cache key (the same approach like [actions/cache](https://github.com/actions/cache/blob/main/examples.md#node---npm) recommends)
- The following key cache will be used `${{ runner.os }}-npm-${{ hashFiles('<package-lock-path>') }}`