feat: Move to Bun monorepo

[ponderingdemocritus]

Description

Currently, the repository uses multiple package managers, which makes it difficult to contribute and get up and running.
I propose migrating to a unified Bun-powered monorepo for faster installs, consistent tooling, and improved testing workflows.

⸻

Proposed Structure

apps/
docs/
examples/
full-examples/
packages/

⸻

Technical Plan
• Use Bun as the single package manager for all apps, examples, and packages.
• Introduce Changesets for versioning, publishing, and release management.
• Unify testing and build commands across the monorepo (bun run test, bun run build, etc.).
• Replace existing npm/yarn/pnpm lockfiles with a single bun.lockb.
• Ensure compatibility with existing CI pipelines.

⸻

Benefits
• ⚡ Speed — ultra-fast installs and builds with Bun.
• 🧩 Consistency — single dependency graph across all packages.
• 🧪 Simplified Testing — shared test runner and environment.
• 🔄 Streamlined Releases — managed via Changesets.
• 👥 Easier Contributions — no setup confusion or package mismatch.

⸻

Next Steps
• Add Bun and Changesets config.
• Migrate existing sub-projects into /apps, /examples, and /packages.
• Test end-to-end setup and adjust CI.
• Document new workflow in CONTRIBUTING.md.

• I am willing to do this migration

[dosco]

1. As far as I know we only use npm for package management I don't think we have multiple package managers.
2. We use vitest for tests and tsup to build and biome for linting and formatting.
3. Finally our mono repo releases are handled by release-it.

I've heard about bun and understand it's new so could have some issues but since we're just a library and not a service it might not matter. What of the above tools would bun replace and I'd to have your thoughts on why bun is better than that tool.

[TheAlexLichter]

The question is always which issues you want to solve here:

• Switching to PNPM or Bun as package manager can speed up installing. PNPM has also excellent monorepo support.
• tsup is in maintenance mode. You can keep using it or think of tsdown instead of tsup which is almost a drop-in replacement.