Skip to content
Closed
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/auth/nextjs-ssr/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
"@crossmint/server-sdk": "workspace:*",
"react": "^18",
"react-dom": "^18",
"next": "15.5.15"
"next": "15.5.18"
},
"devDependencies": {
"typescript": "^5",
Expand Down
2 changes: 1 addition & 1 deletion apps/payments/nextjs/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@
"@dynamic-labs/ethereum": "4.8.3",
"@dynamic-labs/sdk-react-core": "4.8.3",
"@dynamic-labs/solana": "4.8.3",
"next": "15.5.15",
"next": "15.5.18",
"react": "18.3.1",
"react-dom": "18.3.1"
},
Expand Down
2 changes: 1 addition & 1 deletion apps/wallets/quickstart-devkit/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
"clsx": "2.1.1",
"firebase": "^10.3.1",
"firebaseui": "6.1.0",
"next": "15.5.15",
"next": "15.5.18",
"react": "^18",
"react-dom": "^18",
"tailwind-merge": "2.4.0",
Expand Down
2 changes: 1 addition & 1 deletion apps/wallets/react/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
"react-native-web": "~0.21.2",
"@solana/web3.js": "1.98.1",
"@stellar/stellar-sdk": "^14.6.1",
"next": "^16.2.3",
"next": "^15.5.18",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P1 Next.js downgraded from v16 to v15 in this workspace

The pnpm-lock.yaml shows that apps/wallets/react was previously resolving next@16.2.3 (from specifier ^16.2.3). This PR changes the constraint to ^15.5.18, which is a major version downgrade. If any Next.js 16 APIs or features are used in this app, they would break silently at runtime. Please confirm this is intentional and that the app has been tested against Next.js 15.

Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/wallets/react/package.json
Line: 16

Comment:
**Next.js downgraded from v16 to v15 in this workspace**

The `pnpm-lock.yaml` shows that `apps/wallets/react` was previously resolving `next@16.2.3` (from specifier `^16.2.3`). This PR changes the constraint to `^15.5.18`, which is a major version downgrade. If any Next.js 16 APIs or features are used in this app, they would break silently at runtime. Please confirm this is intentional and that the app has been tested against Next.js 15.

How can I resolve this? If you propose a fix, please make it concise.

"react": "^19.0.0",
"react-dom": "^19.0.0",
"viem": "^2.33.1"
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"rimraf": "6.0.1",
"ts-jest": "29.1.1",
"tsup": "8.1.0",
"turbo": "2.2.3",
"turbo": "2.9.14",
"typescript": "5.5.3",
"vitest": "1.6.1",
"vitest-mock-extended": "2.0.2"
Expand Down
2 changes: 1 addition & 1 deletion packages/client/base/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@
"@crossmint/common-sdk-base": "workspace:*",
"@datadog/browser-logs": "6.24.1",
"exponential-backoff": "3.1.1",
"uuid": "9.0.1",
"uuid": "14.0.0",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P1 Large uuid major version jump with several breaking changes

This bumps uuid from 9.0.1 to 14.0.0, spanning five major releases. Key breaking changes across the skipped versions:

  • v12: CommonJS support was removed — the package is now ESM-only. Any consumer using require('uuid') or a bundler configured for CJS will break.
  • v13: Browser exports became the default, which changes module resolution for Node.js consumers unless they explicitly use the node condition.
  • v14: Node.js ≥20 is now required; crypto must be globally available. If the project or its consumers run on Node 18, uuid will throw at runtime.

No direct import ... from 'uuid' was found in packages/client/base/src, so the impact may be limited — but please verify whether any downstream consumer of this package imports uuid via CommonJS or runs on Node 18.

Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/client/base/package.json
Line: 27

Comment:
**Large `uuid` major version jump with several breaking changes**

This bumps `uuid` from `9.0.1` to `14.0.0`, spanning five major releases. Key breaking changes across the skipped versions:

- **v12**: CommonJS support was removed — the package is now ESM-only. Any consumer using `require('uuid')` or a bundler configured for CJS will break.
- **v13**: Browser exports became the default, which changes module resolution for Node.js consumers unless they explicitly use the `node` condition.
- **v14**: Node.js ≥20 is now required; `crypto` must be globally available. If the project or its consumers run on Node 18, `uuid` will throw at runtime.

No direct `import ... from 'uuid'` was found in `packages/client/base/src`, so the impact may be limited — but please verify whether any downstream consumer of this package imports `uuid` via CommonJS or runs on Node 18.

How can I resolve this? If you propose a fix, please make it concise.

"zod": "3.22.4"
},
"devDependencies": {
Expand Down
551 changes: 280 additions & 271 deletions pnpm-lock.yaml

Large diffs are not rendered by default.

Loading