chore(config): the peer range says which eslint the config was built for - #129
Merged
Conversation
`@hopper/config` declared `eslint` as `^10.8.1` in its peerDependencies while the three apps that consume it had moved to `^10.9.1` (#125). The range stayed satisfiable, so nothing broke and nothing warned — but the package no longer said what it was actually built against, and that is the drift that goes unnoticed until a major does break something. `.npmrc` has `strict-peer-dependencies=false`, so peer ranges are the only place this is ever stated. Kept in step by hand, as Dependabot does not follow a peer range when it bumps the dependency itself. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HiQhbiTpvjFnK7CJcJuR9m
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.
@hopper/configdéclaraiteslinten^10.8.1dans sespeerDependenciesalors que les trois applications qui le consomment sont passées à^10.9.1avec le groupe minor (#125).La plage restait satisfaite, donc rien ne cassait et rien n'avertissait — mais le paquet ne disait plus contre quelle version il avait été construit. C'est exactement la dérive qui était passée inaperçue lors de la majeure eslint 10 (#107), où la peer était restée en
^9.35.0: le paquet déclarait alors ne pas savoir fonctionner avec le seul eslint installé, et personne ne l'a vu..npmrcportestrict-peer-dependencies=false, donc les plages de peer sont le seul endroit où cette information est écrite. Dependabot ne suit pas une peer quand il monte la dépendance elle-même, d'où la mise à jour à la main.Vérifié en local
pnpm install --frozen-lockfile,format:check,lint(7/7, les 5 warningsreact-refreshpréexistants),typecheck(7/7),build(5/5),test(7/7).🤖 Generated with Claude Code
https://claude.ai/code/session_01HiQhbiTpvjFnK7CJcJuR9m