deps(dashboard): pin next and eslint-config-next exactly, again - #97
Merged
Conversation
I restored these exact pins during the Next 15 migration and wrote a paragraph about why, then let npm add carets during the Next 16 migration and did not catch it. The reason has not changed: next and eslint-config-next move together, and a caret on one of them is how a lint config drifts away from the framework it configures. Two majors of eslint-config-next apart is how you get a rule set that disagrees with the compiler. Restores 16.3.2 exactly on both, matching every version of this file before today. No resolution change: npm reports the same two packages at the same versions. Lint 0 errors, 99 tests, build produces the route. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Small correction to my own #96.
Both were pinned exactly (
15.5.21) before today. I restored those pins during the Next 15 migration and wrote a paragraph explaining why, then letnpm installadd carets during the Next 16 migration and did not catch it:The reason has not changed. These two move together, and a caret on one is how a lint config drifts away from the framework it configures. Two majors apart is how you get a rule set that disagrees with the compiler.
No resolution change — npm reports the same two packages at the same versions. Lint 0 errors, 99 tests, build produces the route.
🤖 Generated with Claude Code