Add --cache-location option (#13019)
* Implement searching cache file from `--cache-location` option * Add tests * Add docs * Fix * Fix doc * Add changelog * Update snapshots * Update docs * Update docs/cli.md Co-authored-by: Holger Jeromin <mailgithub@katur.de> * Fix changelog * Remove directory support * Update docs * Update tests * Update docs * Add validation for dir * Fix comment * Update option description * Validate JSON * Use `path.resolve` Co-authored-by: Holger Jeromin <mailgithub@katur.de>
This commit is contained in:
1 parent
6e1effadda
commit
955553bb39
10 files changed
+188
-8
No files matched your search
+10
@@ -225,6 +225,16 @@ Also, since the cache file is stored in `./node_modules/.cache/prettier/.prettie
|
||||
|
||||
> Plugins version and implementation are not used as cache keys. We recommend that you delete the cache when updating plugins.
|
||||
|
||||
## `--cache-location`
|
||||
|
||||
Path to the cache file location used by `--cache` flag. If you don't explicit `--cache-location`, Prettier saves cache file at `./node_modules/.cache/prettier/.prettier-cache`.
|
||||
|
||||
If a file path is passed, that file is used as the cache file.
|
||||
|
||||
```bash
|
||||
prettier --write --cache --cache-location=my_cache_file src
|
||||
```
|
||||
|
||||
## `--cache-strategy`
|
||||
|
||||
Strategy for the cache to use for detecting changed files. Can be either `metadata` or `content`.
|
||||
|
||||
Reference in new issue
Block a user