Upgrade Next.js to v16 and update dependencies#241
Conversation
Updated the dependabot.yml file to remove the ignored dependencies for "next" and "@types/node", streamlining the dependency update process.
Updated various dependencies in package.json and package-lock.json, including upgrading "next" to version 16.1.6 and "@filecoin-foundation/ui-filecoin" to version 0.7.5. Modified TypeScript configuration to change JSX setting from "preserve" to "react-jsx" and included additional type definitions for better development support.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
This PR upgrades the project’s Next.js framework version (15 → 16) and aligns related tooling/configuration (React, TypeScript, scripts, dependency automation) to keep the app compatible with the new major release.
Changes:
- Upgraded
nextto16.1.6and updated React/React DOM and their type packages. - Updated Next.js scripts to force Webpack and adjusted TypeScript JSX/
includesettings for Next-generated types. - Simplified Dependabot config by removing ignored dependencies and refreshed the lockfile.
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
tsconfig.json |
Updates JSX mode and expands TS include globs to cover additional Next-generated types. |
package.json |
Bumps Next/React versions and modifies build/dev scripts for Webpack compatibility. |
package-lock.json |
Updates resolved dependency graph for the Next 16 / dependency bumps. |
.github/dependabot.yml |
Removes previously ignored dependencies so Dependabot will update them again. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "frontmatter-markdown-loader": "^3.7.0", | ||
| "gray-matter": "^4.0.3", | ||
| "next": "^15.5.9", | ||
| "next": "16.1.6", |
There was a problem hiding this comment.
next is pinned to an exact version (16.1.6) while most other dependencies use semver ranges (^). If this isn't intentional, consider using a caret range (e.g., ^16.1.6) to allow receiving compatible minor/patch updates (including security fixes) without manual edits.
| "next": "16.1.6", | |
| "next": "^16.1.6", |
| "react": "19.2.4", | ||
| "react-csv": "^2.2.2", | ||
| "react-dom": "^19.2.1", | ||
| "react-dom": "19.2.4", | ||
| "react-markdown": "^10.1.0", |
There was a problem hiding this comment.
react/react-dom are pinned to exact versions while the rest of the dependencies largely use ^ ranges. If there’s no specific need to lock to exact patch versions, switching back to semver ranges helps keep the project up to date with compatible patches automatically.
| "@types/react": "19.2.14", | ||
| "@types/react-csv": "^1.1.10", | ||
| "@types/react-dom": "^19", | ||
| "@types/react-dom": "19.2.3", |
There was a problem hiding this comment.
@types/react and @types/react-dom are pinned to exact versions. If the intent is to track React 19 types over time (similar to other deps), consider using a compatible range (e.g., ^19) to reduce manual maintenance when patch releases land.
1 participant
📝 Description
This PR upgrades the project from Next.js 15 to Next.js 16, along with related dependency updates and TypeScript configuration improvements to ensure compatibility with the latest framework version.
🛠️ Key Changes
🔖 Resources