Remove Bun and migrate tooling to Vite+ - #26
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (92)
📝 WalkthroughWalkthroughThe workspace migrated from Bun-oriented CI, testing, database examples, scripts, and packaging to Vite+, Node.js, Better SQLite, and pnpm. Documentation, migration metadata, Prisma configuration, and example packages were updated accordingly. ChangesVite+ and Node.js tooling
Estimated code review effort: 3 (Moderate) | ~25 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Summary
better-sqlite3for the synchronous Drizzle adaptervp packwhile preserving ESM/CJS, declarations, source maps, and development/production conditional exportsWhy
The repository had moved task orchestration, formatting, and linting to Vite+, but tests, benchmarks, build scripts, SQLite integration tests, and CI still depended on Bun. tsup also duplicated library packaging functionality now provided by Vite+.
This completes the toolchain consolidation so the project uses pnpm, Node.js, and Vite+ consistently. It also removes platform-sensitive fixture symlinks that behaved differently on Windows and Linux.
Impact
There is no intended public API change. The existing package entry points, ESM/CJS formats, declaration files, and development conditional exports are preserved. Historical Prisma 5/6/7 and Drizzle 0.30/0.39/0.44/0.45/1.0 RC compatibility fixtures remain covered.
Updated measured core bundle sizes include:
Validation
vp install --frozen-lockfilevp run checkvp run buildvp run typecheckvp run test— 31 files, 157 testsvp run benchvp run attwvp run build:docsvp run build:examplespnpm peers checkgit diff --checkTypeDoc completes with its existing documentation warnings and no errors.
Summary by CodeRabbit