eslint-plugin-format

Description When the ESLint parser for a file is anything other than (e.g., from another plugin), the rule silently ignores all Prettier plugins passed in the rule options. The formatting runs but plugins don't load — no errors are reported. Additionally, even with , the synckit worker appears to cache Prettier's plugin state from the first invocation. When different file patterns use with different plugin sets (e.g., for and for ), processing them together causes "Failed to format the code" errors on whichever pattern is processed second. Reproduction Bug 1: Plugins ignored without parserPlain Expected: forces all arrays to one-element-per-line. Actual: The plugin is silently ignored. Bug 2: Worker state corruption across file patterns Running alone works. Running (both match different configs above) causes "Failed to format the code" on . Workaround No complete workaround found. Using identical plugin sets across all configs avoids bug 2, but bug 1 prevents using plugins at all when other ESLint plugins (like ) set a non- parser on the same files. Environment eslint-plugin-format: 2.0.1 eslint: 10.1.0 prettier: 3.8.3 Node.js: 24.x

Please be aware that vibe-coding contributions are 🚫 STRICTLY PROHIBITED. We are humans behind these open source projects, trying hard to maintain good quality and a healthy community. Not only do vibe-coding contributions pollute the code, but they also drain A LOT of unnecessary energy and time from maintainers and toxify the community and collaboration. All vibe-coded, AI-generated PRs will be rejected and closed without further notice. In severe cases, your account might be banned organization-wide and reported to GitHub. PLEASE SHOW SOME RESPECT and do not do so. Before submitting the PR, please make sure you do the following: Read the Contributing Guide. Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate. Provide a description in this PR that addresses what the PR is solving and WHY**, or reference the issue that it solves (e.g. ). Ideally, include relevant tests that fail without this PR but pass with it. [x] Linked Issues fixes # Additional context

Clear and concise description of the problem . Suggested solution . Alternative . Additional context . Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.