chore: ⬆️ update dependencies - #111
Conversation
❌ Deploy Preview for better-themes failed.
|
❌ Deploy Preview for demo-better-themes failed.
|
|
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
7 issues found and verified against the latest diff
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="examples/next-app/package.json">
<violation number="1" location="examples/next-app/package.json:32">
P1: The Next.js example's build will fail with this TypeScript version: Next.js 16.2.3 still uses the legacy TypeScript JS API, while TypeScript 7.0.2 omits `typescript/lib/typescript.js`. Keeping the prior TypeScript 6 range (or upgrading Next.js to a release with stable TypeScript 7 support and its required configuration) avoids breaking `next build`.</violation>
</file>
<file name="examples/next-pages/package.json">
<violation number="1" location="examples/next-pages/package.json:32">
P1: Production builds of this Pages example fail with TypeScript 7 because Next 16.2.3's default checker requires the removed `typescript/lib/typescript.js` API. Keeping TypeScript 6, or upgrading to a Next version with the CLI checker and explicitly enabling `experimental.useTypeScriptCli`, avoids the failure.</violation>
</file>
<file name="web/package.json">
<violation number="1" location="web/package.json:23">
P2: This upgrade introduces unmet Fumadocs peer requirements and can cause install warnings or Twoslash/runtime incompatibilities with the older core and UI packages. Retaining the previously compatible Twoslash version or upgrading the Fumadocs packages together would keep the dependency set aligned.</violation>
<violation number="2" location="web/package.json:41">
P1: The `next build`/`types:check` flow will fail during Next.js TypeScript setup even though TypeScript is installed, because Next 16.2.6's default integration depends on the JavaScript compiler API removed in TypeScript 7. Keeping TypeScript 6 for Next's API path (or upgrading to a Next release with TypeScript 7 CLI support and enabling that backend) avoids the failure.</violation>
</file>
<file name="examples/remix/package.json">
<violation number="1" location="examples/remix/package.json:13">
P2: Netlify builds using a Node image below 22.22.0 will fail during dependency installation or build after this upgrade because `@netlify/vite-plugin-react-router@4.0.0` raises the engine requirement. Pinning `NODE_VERSION` to at least 22.22 in the Remix Netlify configuration would make the deployment requirement explicit.</violation>
<violation number="2" location="examples/remix/package.json:38">
P2: TypeScript 7 is outside the peer range declared by the React Router 7.13 packages, producing unmet optional-peer warnings and leaving the React Router type-generation/tooling path on an unsupported compiler major. Using a 5.x TypeScript release or upgrading React Router to a version that declares the selected compiler range would remove the mismatch.</violation>
<violation number="3" location="examples/remix/package.json:39">
P1: The React Router 7.13 toolchain is being paired with an unsupported Vite major: `@react-router/dev@7.13.0` does not declare Vite 8 support, so install reports an unmet peer and the dev/build plugins may fail at runtime. Keeping Vite on 7.x or upgrading all React Router packages to at least the Vite-8-compatible release would avoid the mismatch.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| "tailwindcss": "^4.3.3", | ||
| "tw-animate-css": "^1.4.0", | ||
| "typescript": "^6.0.3" | ||
| "typescript": "^7.0.2" |
There was a problem hiding this comment.
P1: The Next.js example's build will fail with this TypeScript version: Next.js 16.2.3 still uses the legacy TypeScript JS API, while TypeScript 7.0.2 omits typescript/lib/typescript.js. Keeping the prior TypeScript 6 range (or upgrading Next.js to a release with stable TypeScript 7 support and its required configuration) avoids breaking next build.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At examples/next-app/package.json, line 32:
<comment>The Next.js example's build will fail with this TypeScript version: Next.js 16.2.3 still uses the legacy TypeScript JS API, while TypeScript 7.0.2 omits `typescript/lib/typescript.js`. Keeping the prior TypeScript 6 range (or upgrading Next.js to a release with stable TypeScript 7 support and its required configuration) avoids breaking `next build`.</comment>
<file context>
@@ -8,27 +8,27 @@
+ "tailwindcss": "^4.3.3",
"tw-animate-css": "^1.4.0",
- "typescript": "^6.0.3"
+ "typescript": "^7.0.2"
}
}
</file context>
| "typescript": "^7.0.2" | |
| "typescript": "^6.0.3" |
| "tailwindcss": "^4.3.3", | ||
| "tw-animate-css": "^1.4.0", | ||
| "typescript": "^6.0.3" | ||
| "typescript": "^7.0.2" |
There was a problem hiding this comment.
P1: Production builds of this Pages example fail with TypeScript 7 because Next 16.2.3's default checker requires the removed typescript/lib/typescript.js API. Keeping TypeScript 6, or upgrading to a Next version with the CLI checker and explicitly enabling experimental.useTypeScriptCli, avoids the failure.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At examples/next-pages/package.json, line 32:
<comment>Production builds of this Pages example fail with TypeScript 7 because Next 16.2.3's default checker requires the removed `typescript/lib/typescript.js` API. Keeping TypeScript 6, or upgrading to a Next version with the CLI checker and explicitly enabling `experimental.useTypeScriptCli`, avoids the failure.</comment>
<file context>
@@ -8,27 +8,27 @@
+ "tailwindcss": "^4.3.3",
"tw-animate-css": "^1.4.0",
- "typescript": "^6.0.3"
+ "typescript": "^7.0.2"
}
}
</file context>
| "typescript": "^7.0.2" | |
| "typescript": "^6.0.3" |
| "tailwindcss": "^4.3.3", | ||
| "tw-animate-css": "^1.4.0", | ||
| "typescript": "^6.0.3" | ||
| "typescript": "^7.0.2" |
There was a problem hiding this comment.
P1: The next build/types:check flow will fail during Next.js TypeScript setup even though TypeScript is installed, because Next 16.2.6's default integration depends on the JavaScript compiler API removed in TypeScript 7. Keeping TypeScript 6 for Next's API path (or upgrading to a Next release with TypeScript 7 CLI support and enabling that backend) avoids the failure.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At web/package.json, line 41:
<comment>The `next build`/`types:check` flow will fail during Next.js TypeScript setup even though TypeScript is installed, because Next 16.2.6's default integration depends on the JavaScript compiler API removed in TypeScript 7. Keeping TypeScript 6 for Next's API path (or upgrading to a Next release with TypeScript 7 CLI support and enabling that backend) avoids the failure.</comment>
<file context>
@@ -11,33 +11,33 @@
+ "tailwindcss": "^4.3.3",
"tw-animate-css": "^1.4.0",
- "typescript": "^6.0.3"
+ "typescript": "^7.0.2"
}
}
</file context>
| "typescript": "^7.0.2" | |
| "typescript": "^6.0.3" |
| "typescript": "^6.0.3", | ||
| "vite": "^8.0.12", | ||
| "typescript": "^7.0.2", | ||
| "vite": "^8.1.5", |
There was a problem hiding this comment.
P1: The React Router 7.13 toolchain is being paired with an unsupported Vite major: @react-router/dev@7.13.0 does not declare Vite 8 support, so install reports an unmet peer and the dev/build plugins may fail at runtime. Keeping Vite on 7.x or upgrading all React Router packages to at least the Vite-8-compatible release would avoid the mismatch.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At examples/remix/package.json, line 39:
<comment>The React Router 7.13 toolchain is being paired with an unsupported Vite major: `@react-router/dev@7.13.0` does not declare Vite 8 support, so install reports an unmet peer and the dev/build plugins may fail at runtime. Keeping Vite on 7.x or upgrading all React Router packages to at least the Vite-8-compatible release would avoid the mismatch.</comment>
<file context>
@@ -10,33 +10,33 @@
- "typescript": "^6.0.3",
- "vite": "^8.0.12",
+ "typescript": "^7.0.2",
+ "vite": "^8.1.5",
"vite-tsconfig-paths": "^6.1.1"
}
</file context>
| "vite": "^8.1.5", | |
| "vite": "^7.3.6", |
| "fumadocs-core": "16.5.3", | ||
| "fumadocs-mdx": "14.2.6", | ||
| "fumadocs-twoslash": "^3.2.0", | ||
| "fumadocs-twoslash": "^3.3.0", |
There was a problem hiding this comment.
P2: This upgrade introduces unmet Fumadocs peer requirements and can cause install warnings or Twoslash/runtime incompatibilities with the older core and UI packages. Retaining the previously compatible Twoslash version or upgrading the Fumadocs packages together would keep the dependency set aligned.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At web/package.json, line 23:
<comment>This upgrade introduces unmet Fumadocs peer requirements and can cause install warnings or Twoslash/runtime incompatibilities with the older core and UI packages. Retaining the previously compatible Twoslash version or upgrading the Fumadocs packages together would keep the dependency set aligned.</comment>
<file context>
@@ -11,33 +11,33 @@
"fumadocs-core": "16.5.3",
"fumadocs-mdx": "14.2.6",
- "fumadocs-twoslash": "^3.2.0",
+ "fumadocs-twoslash": "^3.3.0",
"fumadocs-ui": "16.5.0",
- "lucide-react": "^1.14.0",
</file context>
| "tw-animate-css": "^1.4.0", | ||
| "typescript": "^6.0.3", | ||
| "vite": "^8.0.12", | ||
| "typescript": "^7.0.2", |
There was a problem hiding this comment.
P2: TypeScript 7 is outside the peer range declared by the React Router 7.13 packages, producing unmet optional-peer warnings and leaving the React Router type-generation/tooling path on an unsupported compiler major. Using a 5.x TypeScript release or upgrading React Router to a version that declares the selected compiler range would remove the mismatch.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At examples/remix/package.json, line 38:
<comment>TypeScript 7 is outside the peer range declared by the React Router 7.13 packages, producing unmet optional-peer warnings and leaving the React Router type-generation/tooling path on an unsupported compiler major. Using a 5.x TypeScript release or upgrading React Router to a version that declares the selected compiler range would remove the mismatch.</comment>
<file context>
@@ -10,33 +10,33 @@
"tw-animate-css": "^1.4.0",
- "typescript": "^6.0.3",
- "vite": "^8.0.12",
+ "typescript": "^7.0.2",
+ "vite": "^8.1.5",
"vite-tsconfig-paths": "^6.1.1"
</file context>
| "typescript": "^7.0.2", | |
| "typescript": "^5.9.3", |
| "@radix-ui/react-label": "^2.1.8", | ||
| "@radix-ui/react-radio-group": "^1.3.8", | ||
| "@radix-ui/react-slot": "^1.2.4", | ||
| "@netlify/vite-plugin-react-router": "^4.0.0", |
There was a problem hiding this comment.
P2: Netlify builds using a Node image below 22.22.0 will fail during dependency installation or build after this upgrade because @netlify/vite-plugin-react-router@4.0.0 raises the engine requirement. Pinning NODE_VERSION to at least 22.22 in the Remix Netlify configuration would make the deployment requirement explicit.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At examples/remix/package.json, line 13:
<comment>Netlify builds using a Node image below 22.22.0 will fail during dependency installation or build after this upgrade because `@netlify/vite-plugin-react-router@4.0.0` raises the engine requirement. Pinning `NODE_VERSION` to at least 22.22 in the Remix Netlify configuration would make the deployment requirement explicit.</comment>
<file context>
@@ -10,33 +10,33 @@
- "@radix-ui/react-label": "^2.1.8",
- "@radix-ui/react-radio-group": "^1.3.8",
- "@radix-ui/react-slot": "^1.2.4",
+ "@netlify/vite-plugin-react-router": "^4.0.0",
+ "@radix-ui/react-aspect-ratio": "^1.1.11",
+ "@radix-ui/react-label": "^2.1.11",
</file context>
There was a problem hiding this comment.
1 issue found across 1 file (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="pnpm-workspace.yaml">
<violation number="1" location="pnpm-workspace.yaml:9">
P2: These exclusions bypass pnpm 11's default 24-hour minimum-release-age quarantine for four newly selected versions. Unless each release is intentionally and independently vetted, keeping them weakens the repository's supply-chain protection; waiting for the age window or documenting a verified exception would retain that protection.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| "@parcel/watcher": false | ||
| esbuild: false | ||
| sharp: false | ||
| minimumReleaseAgeExclude: |
There was a problem hiding this comment.
P2: These exclusions bypass pnpm 11's default 24-hour minimum-release-age quarantine for four newly selected versions. Unless each release is intentionally and independently vetted, keeping them weakens the repository's supply-chain protection; waiting for the age window or documenting a verified exception would retain that protection.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At pnpm-workspace.yaml, line 9:
<comment>These exclusions bypass pnpm 11's default 24-hour minimum-release-age quarantine for four newly selected versions. Unless each release is intentionally and independently vetted, keeping them weakens the repository's supply-chain protection; waiting for the age window or documenting a verified exception would retain that protection.</comment>
<file context>
@@ -6,3 +6,8 @@ allowBuilds:
"@parcel/watcher": false
esbuild: false
sharp: false
+minimumReleaseAgeExclude:
+ - "@tanstack/react-start-rsc@0.1.30"
+ - "@tanstack/react-start@1.168.31"
</file context>
1 participant
Summary by cubic
Update dependencies across the monorepo to current stable versions, set the workspace to
pnpm@11.15.0, and adjustpnpm-workspace.yamlto allow a few fresh packages. No app logic changes; examples and site build with newer tooling.Dependencies
react/react-dom19.2.7; Radix UI packages;lucide-react1.25.0.typescript7.0.2,tailwindcss4.3.3,@tailwindcss/*,postcss8.5.20.vite8.1.5,@vitejs/plugin-react6.0.3.fumadocs-*,twoslash,isbot.packageManagertopnpm@11.15.0,turbo2.10.5,@changesets/cli2.31.1, refreshed lockfile,pnpm-workspace.yamlformatting, andminimumReleaseAgeExcludeentries for select TanStack packages andpostcssto unblock installs.Migration
pnpm@11.15.0and runpnpm i.rm -rf node_modules .turbo) and rebuild.Written for commit e304c50. Summary will update on new commits.