From 5fddb2d5101a1d50d5a55586ac2fded054bf56e7 Mon Sep 17 00:00:00 2001 From: Maxim Lobanov Date: Mon, 24 May 2021 17:35:10 +0300 Subject: [PATCH] Update 0000-caching-dependencies.md --- docs/adrs/0000-caching-dependencies.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/adrs/0000-caching-dependencies.md b/docs/adrs/0000-caching-dependencies.md index c8c24c5..16193f7 100644 --- a/docs/adrs/0000-caching-dependencies.md +++ b/docs/adrs/0000-caching-dependencies.md @@ -30,6 +30,7 @@ We don't persue the goal to provide wide customization of caching in scope of `a - 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('') }}` +- Action will cache global npm cache directory (retrieved via `npm config get cache`) # Example of real use-cases Default use case when `package-lock.json` or `yarn.lock` are located in repository root: