Repository navigation
Conversation
Signed-off-by: Baylem <zelathis@gmail.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 39 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
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
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 dashboard uses ESLint and
@eslint/js9.39.5 with TypeScript 6.0.3. The dependency inventory listed the ESLint 10 preset, and the upgrade instructions pointed to superseded PRs. This updates the documented versions and explains why the three current Dependabot PRs need coordinated migrations.eslint-plugin-react@7.37.5calls the removedcontext.getFilename()API while loadingreact/display-name. Updating the JS preset alone gives it an installed ESLint 9 peer outside its supported range. Upgrade the plugin, engine and preset together. Upstream compatibility patchVerified the documented ranges against
web/package.jsonand the resolved versions againstweb/package-lock.json. A one-line JSX fixture passed on ESLint 9.39.5 and failed on 10.14.0 with the same React settings. On #628’s lockfile,npm ls --package-lock-only eslint @eslint/jsreported the invalid peer. The change is documentation-only.