prettier / prettier/prettier-cli

Experimental CLI reports about cache-strategy settings

Open
#72 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
43
Forks
10
Avg merge
18m
Merged PRs (30d)
1

Description

Environments:*

  • Prettier Version: 3.6.0
  • Running Prettier via: CLI
  • Runtime:
  • Operating System: Windows

Steps to reproduce:

prettier 3.5.3 works with this command line:

..\node_modules\.bin\prettier.cmd --ignore-path ../.prettierignore --cache --cache-strategy metadata --cache-location ../node_modules/.cache/prettier/.prettier-cache --check .

Prettier 3.6.0

..\node_modules\.bin\prettier.cmd --ignore-path ../.prettierignore --experimental-cli --cache --cache-strategy metadata --cache-location ../node_modules/.cache/prettier/.prettier-cache --check .

The "--cache-strategy" option has been deleted, since the "metadata" strategy is no longer supported

Ah, ok. changed strategy:

..\node_modules\.bin\prettier.cmd --ignore-path ../.prettierignore --experimental-cli --cache --cache-strategy content --cache-location ../node_modules/.cache/prettier/.prettier-cache --check .

The "--cache-strategy" option has been deleted, since the "metadata" strategy is no longer supported

Hu?

..\node_modules\.bin\prettier.cmd --ignore-path ../.prettierignore --experimental-cli --cache --cache-location ../node_modules/.cache/prettier/.prettier-cache --check .

works...

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Windows CLI commands in the issue, comparing the runs with --cache-strategy metadata, --cache-strategy content, and no strategy flag. Trace the experimental CLI's cache-option handling and any related tests or entry points it exposes. Done means the reported strategy behavior is either corrected or clearly verified against the supported options.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.