[richardsolomou]

Problem

I have to coordinate shared dependency versions and repeated build/tool configuration with RAS and its separate configuration package.

Changes

I selected configured capabilities in ras.config.ts. RAS supplies React, Tailwind/animations, PostHog source-map wiring, and compiler/linter presets. Application-specific configuration and plain libraries remain here.

Selected packages stay visible as ordinary exact dependencies. Build/test tools and types are development dependencies; RAS shares runtime SDKs through optional peers. ras sync updates owned manifest entries, committed .ras presets, and marked Dependabot ignores, then calls pnpm. ras update runs the target release's sync and installation in one command. CI uses a normal frozen install and read-only sync verification. There are no dependency-injection hooks or formatter exclusions.

This draft pins [email protected] from RAS v5. The seven-day release-age policy remains enabled with exact reviewed exceptions. Managed updates require a coordinated RAS upgrade; security alerts remain visible and app-owned packages remain eligible for Dependabot updates.

Risk

Medium. Dependency ownership, build configuration, and Vitest's major version change. Replace the prerelease with stable RAS v5 and run sync before merging. Reverting this PR restores the previous dependency ownership and build configuration.

Verification

• just check: formatting, read-only sync verification, lint, Changesets validation, typecheck, 504 tests, and production build passed against the candidate.
• just e2e: all 71 Chromium tests passed against the production build, including real exports.
• Fresh native frozen installation and peer checks passed. Committed presets require no preparation step.
• Actionlint, Markdown lint, and git diff --check passed. The existing large-bundle warning remains.
• Production deployment was not exercised.

Checklist

• Tests cover new or changed behavior where practical.
• Geometry changes are checked against a real export, not just the preview. (N/A: no geometry changes; existing export tests passed.)
• User-facing behavior is documented in the README. (N/A: tooling-only; setup is documented in CONTRIBUTING.)

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	basekit	b969156	Commit Preview URL Branch Preview URL	Oct 21 2026, 05:48 PM