feat: Upgrade Vite to 8.0.16, Node to 24.17.0, and pnpm to 11.7.0

[kingston]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: 6c58b46

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 24 packages

Name	Type
@baseplate-dev/project-builder-dev	Patch
@baseplate-dev/core-generators	Patch
@baseplate-dev/react-generators	Patch
@baseplate-dev/project-builder-test	Patch
@baseplate-dev/fastify-generators	Patch
@baseplate-dev/project-builder-server	Patch
@baseplate-dev/plugin-ai	Patch
@baseplate-dev/plugin-auth	Patch
@baseplate-dev/plugin-email	Patch
@baseplate-dev/plugin-observability	Patch
@baseplate-dev/plugin-payments	Patch
@baseplate-dev/plugin-queue	Patch
@baseplate-dev/plugin-rate-limit	Patch
@baseplate-dev/plugin-storage	Patch
@baseplate-dev/create-project	Patch
@baseplate-dev/project-builder-cli	Patch
@baseplate-dev/project-builder-common	Patch
@baseplate-dev/project-builder-web	Patch
@baseplate-dev/code-morph	Patch
@baseplate-dev/project-builder-lib	Patch
@baseplate-dev/sync	Patch
@baseplate-dev/tools	Patch
@baseplate-dev/ui-components	Patch
@baseplate-dev/utils	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Warning

Review limit reached

@kingston, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 34 minutes and 30 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7f93a0a3-b856-4cf7-b547-739a426bffef

📥 Commits

Reviewing files that changed from the base of the PR and between 5cfc51e and 6c58b46.

⛔ Files ignored due to path filters (12)

• examples/blog-with-auth/apps/admin/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
• examples/blog-with-auth/apps/backend/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
• examples/blog-with-auth/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
• examples/blog-with-auth/libs/transactional/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
• examples/blog-with-auth/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
• examples/todo-with-better-auth/apps/admin/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
• examples/todo-with-better-auth/apps/backend/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
• examples/todo-with-better-auth/apps/web/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
• examples/todo-with-better-auth/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
• examples/todo-with-better-auth/libs/transactional/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
• examples/todo-with-better-auth/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (27)

• .changeset/all-bats-jam.md
• .changeset/upgrade-vite-node-pnpm.md
• .node-version
• .nvmrc
• examples/blog-with-auth/Dockerfile
• examples/blog-with-auth/apps/admin/package.json
• examples/blog-with-auth/apps/backend/package.json
• examples/blog-with-auth/libs/transactional/package.json
• examples/blog-with-auth/package.json
• examples/todo-with-better-auth/CLAUDE.md
• examples/todo-with-better-auth/Dockerfile
• examples/todo-with-better-auth/apps/admin/package.json
• examples/todo-with-better-auth/apps/backend/package.json
• examples/todo-with-better-auth/apps/web/package.json
• examples/todo-with-better-auth/libs/transactional/package.json
• examples/todo-with-better-auth/package.json
• mise.toml
• package.json
• packages/core-generators/package.json
• packages/core-generators/src/constants/core-packages.ts
• packages/core-generators/src/constants/node.ts
• packages/project-builder-dev/package.json
• packages/project-builder-server/package.json
• packages/project-builder-web/package.json
• packages/react-generators/src/constants/react-packages.ts
• packages/ui-components/package.json
• pnpm-workspace.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kingston/eng-1165-feat-upgrade-vite-to-8016-and-node-to-24170

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	testcontainers@​12.0.2
	vite@​8.0.14 ⏵ 8.0.16	+1	+18	+1
	semver@​7.8.4

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (npm metadata) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/package.json) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: examples/todo-with-better-auth/pnpm-lock.yaml → npm/@tanstack/router-plugin@1.159.5 → npm/@storybook/react-vite@10.4.1 → npm/@graphql-codegen/cli@7.1.0 → npm/@graphql-eslint/eslint-plugin@4.4.0 → npm/vite-plugin-svgr@4.5.0 → npm/eslint-plugin-react-hooks@7.0.1 → npm/eslint-plugin-unicorn@62.0.0 → npm/caniuse-lite@1.0.30001799 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001799. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: examples/todo-with-better-auth/pnpm-lock.yaml → npm/eslint@9.39.2 → npm/knip@5.79.0 → npm/react-diff-viewer-continued@4.2.0 → npm/@graphql-codegen/cli@7.1.0 → npm/check-dependency-version-consistency@5.0.0 → npm/@graphql-eslint/eslint-plugin@4.4.0 → npm/vite-plugin-svgr@4.5.0 → npm/js-yaml@4.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cloudflare-workers-and-pages]

Deploying baseplate-storybook with    Cloudflare Pages

Latest commit:	6c58b46
Status:	🚫  Build failed.

View logs