Repository navigation
Upgrade to Next 16 / React 19 to clear security advisories - #18
Merged
Merged
Conversation
Next 14.2.35 carried a critical and a high advisory, and its PostCSS, nanoid and source-map-js versions carried high ones. This moves to Next 16.4, React 19.3, PostCSS 8.5.29 and Vitest 5 (Vitest 3 pulled in a critical tinypool advisory), with @types/node 22 to match CI. Production dependencies now audit clean. The broken `lint` script is removed (Next 16 dropped `next lint`), and five spots get the React 19 ref and JSX type changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
3 of 4 tasks
This branch was successfully deployed
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.
Why
npm auditonmainreported 1 critical and 3 high vulnerabilities in production dependencies:Vitest 3 also pulled in a critical
tinypooladvisory in development.What changes
package-lock.jsonis regenerated. npm 11.0.0 crashed on the Vitest 5 peer set (edgesOut); npm 11.21 resolves it.lintscript is removed. It was already broken (ESLint is not installed), and Next 16 droppednext lint.tsconfig.json: Next 16's own changes (jsx: react-jsx, plus.next/dev/types).RefObject<T | null>,JSXimported fromreact, anduseRefgiven an initial value.Audit after
npm audit --omit=dev: 0 vulnerabilities.braces,micromatch,chokidar,fast-glob,postcss-selector-parser). They run only at build time on our own config, never in the browser or the server function. Clearing them needs the Tailwind 4 migration, which is a separate change.Test plan
npx tsc --noEmit,npm test(1034 passed on Vitest 5),npm run build(Next 16, Turbopack)🤖 Generated with Claude Code