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 apps/web/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@
"keyv": "npm:@keyvhq/core@~1.6.26",
"lucide-react": "^0.477.0",
"motion": "^12.23.12",
"next": "^15.5.8",
"next": "^16.1.5",
Copy link

Choose a reason for hiding this comment

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

Peer dependency mismatch after Next.js major upgrade

Medium Severity

Upgrading next to 16.1.5 while @next/third-parties remains at ^15.5.8 creates a peer dependency conflict. The @next/[email protected] package declares a peer dependency of next: ^13.0.0 || ^14.0.0 || ^15.0.0, which does not include Next.js 16.x. This mismatch could cause runtime errors or unexpected behavior with third-party integrations like Google Analytics, Google Maps, or YouTube embeds.

Fix in Cursor Fix in Web

Copy link

Choose a reason for hiding this comment

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

Sentry integration incompatible with Next.js 16 upgrade

Medium Severity

The @sentry/[email protected] package has a peer dependency of next: ^13.2.0 || ^14.0 || ^15.0.0-rc.0, which does not include Next.js 16.x. Upgrading next to 16.1.5 while keeping @sentry/nextjs at ^9.46.0 creates a peer dependency conflict. This could cause Sentry's error tracking, source map uploads, or server-side error capturing to malfunction or fail silently in production.

Fix in Cursor Fix in Web

"next-themes": "^0.4.6",
"pako": "^2.1.0",
"postcss": "^8.5.6",
Expand Down
Loading
Loading