Repository navigation
Put every repository on the same Prettier and ESLint - #75
Merged
Merged
Conversation
The fleet keeps its formatting configuration identical on purpose, and the shared scripts byte identical, but the tools reading them had drifted to three Prettier versions and four of ESLint. That is not academic: 3.9.9 prints the shared test-db harness differently from 3.9.6, so the copies could not both pass `format:check` and stay identical, and the repository that noticed was the one that happened to install the newer one. Prettier 3.9.9 and ESLint 10.11.0 everywhere, which is what npm serves today. No file changed format under the newer Prettier, so the gap was latent rather than already divergent.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The fleet keeps its formatting configuration identical and its shared scripts byte identical, but the tools reading them had drifted. Three Prettier versions and four of ESLint were installed across seven repositories. That is not academic. Prettier 3.9.9 prints the shared test-db harness differently from 3.9.6, so the copies could not both pass
format:checkand stay identical.Prettier 3.9.9 and ESLint 10.11.0, which is what npm serves today. No file changed format under the newer Prettier, so the gap was latent rather than already divergent. Nothing else moves.
pnpm install.pnpm verify.git diffshows no formatting changes.