Repository navigation
Update browserslist, Next.js, and ESLint - #10355
Merged
Merged
Conversation
Bump browserslist 4.28.2 -> 4.28.8 to pick up the latest release. It comes in transitively via @babel/helper-compilation-targets (from @babel/core, pulled by eslint-plugin-react-hooks and react-docgen), so updating Next.js alone does not move it: Yarn keeps the existing resolution for the unchanged ^4.24.0 descriptor. Also bump Next.js 16.3.2 -> 16.3.3 (next, @next/mdx, eslint-config-next) and ESLint 9.39.4 -> 9.39.5. Next 16.3.4 and Storybook 10.6.0 are held back by the 7-day npmMinimalAgeGate in .yarnrc.yml; Storybook 10.5.10 is already the newest eligible release. ESLint 10 is not yet viable: eslint-plugin-react still calls the removed context.getFilename() API, which crashes config loading via eslint-config-next. Verified with yarn install --immutable, eslint, yarn build, build-storybook, 303 Playwright visual snapshots, and format:check.
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The changes are consistent patch-level dependency bumps with a corresponding lockfile update and no functional code modifications.
Pull request overview
Updates the website’s frontend toolchain dependencies to newer patch versions, primarily to keep the Next.js stack, ESLint, and Browserslist-related transitive packages current.
Changes:
- Bump
nextand@next/mdxfrom16.3.2→16.3.3. - Bump
eslint-config-nextfrom16.3.2→16.3.3, and refresh related ESLint packages in the lockfile. - Update Browserslist and its transitive data packages (e.g.,
caniuse-lite,electron-to-chromium,node-releases,update-browserslist-db) via lockfile refresh.
File summaries
| File | Description |
|---|---|
website/package.json |
Updates declared Next.js and ESLint-related dependency versions to newer patch releases. |
website/yarn.lock |
Regenerates lock entries to reflect the updated Next.js/ESLint versions and the refreshed Browserslist dependency graph. |
Review details
- Files reviewed: 1/2 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Bump every direct dependency that has a newer release permitted by the 7-day npmMinimalAgeGate: @docsearch/css, @docsearch/react 4.7.0 -> 5.0.4 @types/node 24.13.3 -> 26.4.0 @xyflow/react 12.11.3 -> 12.11.5 elkjs 0.11.1 -> 0.12.0 js-yaml 5.3.0 -> 5.4.1 sharp 0.35.3 -> 0.35.4 @types/react-dom 19.2.4 -> 19.2.5 DocSearch v5 drops onAskAiToggle from the base modal's props (it now lives on the Ask-AI modal variant only), so remove the no-op handler that was passed to DocSearchModal; the hook still takes it and is left as is. v5 also drops --docsearch-searchbox-shadow, so drop that now-dead override: focus styling comes from --docsearch-searchbox-focus-background and --docsearch-highlight-color, both already mapped to the accent. Two majors are held back. TypeScript 7 breaks @typescript-eslint's typescript-estree ("Cannot read properties of undefined (reading 'Cjs')"), which crashes ESLint via eslint-config-next. ESLint 10 crashes for a different reason: eslint-plugin-react still calls the removed context.getFilename() API. Both stay on their current majors. Verified with yarn install --immutable, eslint, tsc --noEmit, yarn build, build-storybook, 303 Playwright visual snapshots, and format:check.
This was referenced Oct 25, 2026
Merged
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.
No description provided.