Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
"bcryptjs": "^2.4.3",
"classnames": "^2.3.1",
"lodash": "^4.17.21",
"next": "^12.0.5",
"next": "^15.5.10",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This major version upgrade from ^12.0.5 to ^15.5.10 will introduce significant breaking changes and is highly likely to break the application. The Snyk report itself flags this as a breaking change.

Key issues include:

  1. React Version Incompatibility: Next.js v13 and later versions require React 18. This project currently uses React 17. The build will fail without upgrading react and react-dom and adapting the code to React 18's new features, like the root API.

  2. Deprecated next.config.js Options: Your next.config.js uses options like target: 'experimental-serverless-trace' and the future.webpack5 flag, which are deprecated or removed in newer Next.js versions. These will need to be updated to their modern equivalents (e.g., the output option).

  3. Suspicious Target Version: The target version 15.5.10 is questionable, as the latest stable Next.js version is v14.x. The vulnerability this PR aims to fix (SNYK-JS-NEXT-15104645) is patched in version 14.1.1.

Due to these issues, a direct merge is not feasible. A manual migration, carefully addressing the breaking changes between major Next.js versions (12 -> 13 -> 14), is required.

"next-auth": "4.0.0-beta.6",
"next-connect": "^0.10.2",
"react": "^17.0.2",
Expand Down
Loading
Loading