[template-sync] Sync with nuxt-ui-templates/saas — 2026-03-30#130
[template-sync] Sync with nuxt-ui-templates/saas — 2026-03-30#130github-actions[bot] wants to merge 1 commit intomainfrom
Conversation
Update dependencies to match upstream template: - typescript: ^5.9.3 → ^6.0.2 - pnpm: 10.29.2 → 10.33.0 - nuxt: ^4.2.2 → ^4.4.2 - @nuxt/ui: ^4.4.0 → ^4.6.0 - @nuxt/content: ^3.11.2 → ^3.12.0 - @nuxt/eslint: ^1.15.1 → ^1.15.2 - better-sqlite3: ^12.6.2 → ^12.8.0 - eslint: ^10.0.3 → ^10.1.0 - vue-tsc: ^3.2.4 → ^3.2.6 - @iconify-json/lucide: ^1.2.90 → ^1.2.100 - @iconify-json/simple-icons: ^1.2.70 → ^1.2.75 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Syncs this Nuxt 4 / Nuxt UI v4 blog template with upstream nuxt-ui-templates/saas by applying dependency/tooling upgrades (notably TypeScript 6 and pnpm 10.33.0) and refreshing the lockfile/state to the latest upstream commit.
Changes:
- Upgraded core framework/tooling dependencies (Nuxt, Nuxt UI, Nuxt Content, ESLint, TypeScript, pnpm).
- Regenerated
pnpm-lock.yamlto reflect the updated dependency graph. - Updated template sync state to the latest upstream commit SHA.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| package.json | Bumps Nuxt/Nuxt modules and dev tooling versions; updates packageManager pin to pnpm@10.33.0. |
| pnpm-lock.yaml | Lockfile refresh consistent with the upgraded dependencies (Nuxt 4.4.2, Nuxt UI 4.6.0, TypeScript 6.0.2, etc.). |
| .github/template-sync-state.json | Records the new upstream lastSyncedCommit SHA for template-sync tracking. |
| "typescript": "^5.9.3", | ||
| "vue-tsc": "^3.2.4" | ||
| "eslint": "^10.1.0", | ||
| "typescript": "^6.0.2", |
There was a problem hiding this comment.
@nuxt/ui@4.6.0 declares typescript: ^5.6.3 as a peer dependency, but this PR upgrades TypeScript to ^6.0.2. Even if CI currently passes, this will produce an incompatible peer dependency warning (and can lead to subtle type/tooling issues). Consider either keeping TypeScript on a compatible v5 range until Nuxt UI supports v6, or adding an explicit pnpm peer-dependency rule/override so installs are deterministic and the mismatch is intentionally handled.
| "typescript": "^6.0.2", | |
| "typescript": "^5.6.3", |
| "just-kebab-case": "^4.2.0", | ||
| "nuxt": "^4.2.2", | ||
| "nuxt": "^4.4.2", | ||
| "posthog-js": "^1.345.2", |
There was a problem hiding this comment.
Nuxt 4.4.2 (and related packages like @nuxt/ui@4.6.0) now require Node ^20.19.0 || >=22.12.0 (per their engines field). Since this repo doesn't declare a "engines" constraint in package.json, developers on older Node 20.x patch versions may hit install/runtime failures without a clear message. Consider adding an engines.node entry matching the new minimum to make the requirement explicit and enforceable.
Syncs dependency upgrades from upstream nuxt-ui-templates/saas, primarily the upgrade of TypeScript to v6 and pnpm to 10.33.0.
Upstream compare: nuxt-ui-templates/saas@d548b61...5132651
Changed files
package.jsonpnpm-lock.yamlpackage.jsonupdate.github/template-sync-state.jsonlastSyncedCommitset to51326517c04ab00413e42c63bd015c92f84588fdDependency changes
typescript^5.9.3^6.0.2pnpm10.29.210.33.0nuxt^4.2.2^4.4.2@nuxt/ui^4.4.0^4.6.0@nuxt/content^3.11.2^3.12.0@nuxt/eslint^1.15.1^1.15.2better-sqlite3^12.6.2^12.8.0eslint^10.0.3^10.1.0vue-tsc^3.2.4^3.2.6@iconify-json/lucide^1.2.90^1.2.100@iconify-json/simple-icons^1.2.70^1.2.75Validation
pnpm typecheck— passed with no errorspnpm lint— passed with no errors