Skip to content

fix(deps): downgrade nextjs#1200

Merged
waleedlatif1 merged 1 commit intostagingfrom
fix/nextjs
Aug 30, 2025
Merged

fix(deps): downgrade nextjs#1200
waleedlatif1 merged 1 commit intostagingfrom
fix/nextjs

Conversation

@waleedlatif1
Copy link
Collaborator

Summary

downgrade nextjs because bun bundling is incompatible with nextjs 15

Type of Change

  • Bug fix

Testing

downgrade nextjs

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel
Copy link

vercel bot commented Aug 30, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Aug 30, 2025 4:44am
sim Building Building Preview Comment Aug 30, 2025 4:44am

@waleedlatif1 waleedlatif1 merged commit df3d532 into staging Aug 30, 2025
3 of 4 checks passed
@waleedlatif1 waleedlatif1 deleted the fix/nextjs branch August 30, 2025 04:44
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Greptile Summary

This PR claims to downgrade Next.js to fix Bun bundling compatibility issues, but actually upgrades Next.js from version ^15.3.2 to ^15.4.1. The changes add package overrides in both the root package.json and apps/sim/package.json to enforce specific versions of Next.js and @next/env across the entire dependency tree.

The key changes include:

  • Moving Next.js version from ^15.3.2 to ^15.4.1 in both package files
  • Adding overrides sections to force consistent versions across all workspace packages
  • Moving @next/env from devDependencies to the overrides section in the root package.json

The overrides mechanism ensures all transitive dependencies use the specified versions, which can help resolve version conflicts. However, this contradicts the stated goal since upgrading to a newer Next.js version is unlikely to resolve compatibility issues with Bun that were present in the previous version.

PR Description Notes:

  • The PR title says "downgrade nextjs" but the change is actually an upgrade
  • The description claims incompatibility with "nextjs 15" but upgrades within the Next.js 15 series
  • Testing section just repeats "downgrade nextjs" without specific test details

Confidence score: 1/5

  • This PR has a fundamental contradiction between intent and implementation that could cause production issues
  • Score reflects the mismatch between claimed downgrade and actual upgrade, which may not resolve the stated Bun compatibility issues
  • Both package.json files require immediate attention to verify the correct Next.js version needed for Bun compatibility

2 files reviewed, 2 comments

Edit Code Review Bot Settings | Greptile

"mammoth": "^1.9.0",
"mysql2": "3.14.3",
"next": "^15.3.2",
"next": "^15.4.1",
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: Version changed from ^15.3.2 to ^15.4.1 - this is an upgrade, not a downgrade as claimed in PR title/description

Comment on lines +31 to +32
"next": "^15.4.1",
"@next/env": "^15.4.1"
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: This upgrades Next.js from 15.3.2 to 15.4.1, contradicting the PR title claiming a 'downgrade'. If Bun has compatibility issues with Next.js 15, upgrading to a newer 15.x version may not resolve the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant