René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`rs fmt` cache misses changes to files read by 3rd-party prettier plugins","articleBody":"## Problem\n\nFor example, `prettier-plugin-tailwindcss` sorts classes based on the stylesheet set by `tailwindStylesheet`. After that stylesheet changes, `rs fmt --check` can still pass because the cache is hit, while `rs fmt --check --no-cache` fails.\n\nOur cache is on by default, this is actually a correctness issue. But it's hard to resolve:\n\n- Prettier has no API for plugins to report the files they depend on.\n- The referenced files can pull in more files, such as Tailwind's `@import`, `@plugin`, and `@source`.\n\nUpstream `prettier --cache` and `@prettier/cli` have the same limitation.\n\n## Possible solutions\n\n1. **Disable the cache when third-party plugins are configured.** Skip the cache for files whose options include plugins from `plugins`. This is always correct, at the cost of losing the cache for those projects. It can be combined with option 3 so users can opt back in.\n2. **Special-case common plugins.** For plugins such as `prettier-plugin-tailwindcss`, include the content of files referenced by known options (`tailwindStylesheet`, `tailwindConfig`) and the installed `tailwindcss` version in the cache key. This covers the most common case without configuration, but cannot be complete.\n3. **Let users declare extra cache inputs.** Add an option to `define.fmt()` whose file contents are included in the cache key, for example `cacheInputs: ['./src/app.css']`.\n","author":{"url":"https://github.com/elecmonkey","@type":"Person","name":"elecmonkey"},"datePublished":"2026-11-02T09:03:24Z","url":"https://github.com/rstackjs/rstack-cli/issues/609"}