feat: add the sample-expo-kit-fullstack reference sample - #8
Conversation
59bf346 to
596ae38
Compare
|
This pull request has been automatically marked as stale because it has not had any activity for 7 days. It will be closed in 7 days if no further activity occurs. If you believe this PR is still relevant, please add a comment or push new commits to keep it open. Thank you for your contributions! |
|
This pull request has been automatically marked as stale because it has not had any activity for 7 days. It will be closed in 7 days if no further activity occurs. If you believe this PR is still relevant, please add a comment or push new commits to keep it open. Thank you for your contributions! |
fdafb70 to
48bb1c0
Compare
|
This pull request has been automatically marked as stale because it has not had any activity for 7 days. It will be closed in 7 days if no further activity occurs. If you believe this PR is still relevant, please add a comment or push new commits to keep it open. Thank you for your contributions! |
48bb1c0 to
dba766f
Compare
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueComment |
dba766f to
3acfdbf
Compare
beeman
changed the title
3acfdbf to
3a5d8f6
Compare
A Bun-only full-stack reference sample: an Expo mobile app, a TanStack Start web app, and a Hono API sharing one Drizzle database, one Better Auth layer, and one Solana Kit client across a Turborepo monorepo. Internal packages live under the `@repo` scope, agent skills come from `create-solana-dapp` rather than a checked-in Ruler configuration, and the sample is tested with Bun only. The web app builds its Kit 8 client per cluster with `@solana/kit-plugin-rpc` and `@solana/kit-plugin-wallet` and reads it through `@solana/react`. The API holds a read-only client that installs `rpc` and `rpcSubscriptions` from `SOLANA_ENDPOINT` and nothing else, so signing and sending only ever happen against the user's wallet.
3a5d8f6 to
53c93c6
Compare
1 participant
A Bun-only full-stack reference sample: an Expo mobile app, a TanStack Start web app, and a Hono API sharing one Drizzle database, one Better Auth layer, and one Solana Kit client across a Turborepo monorepo. Internal packages live under the
@reposcope so renaming a scaffolded project never rewrites an import.Agent skills come from
create-solana-dapprather than a checked-in Ruler configuration. Each entry points at a single skill in its upstream repository:ai-sdkbetter-auth-best-practicesheroui-nativehonosolana-devsolana-mobile-devturborepovercel-composition-patternsvercel-react-best-practicesvercel-react-native-skillsweb-design-guidelinesThe sample declares
packageManager: "bun", so scaffolding with npm, pnpm, or Yarn fails with a clear message, and the template test matrix runs it under Bun only. Bun is pinned at 1.4.0 in.bun-version,packageManager, both Dockerfiles, and the@types/buncatalog entry. Root Prettier ignores the directory so its Biome formatting survives.Scaffolding renames the sample end to end: the app identity matches the package name, so the Android package id becomes
com.anonymous.<project_name>rather than keeping the sample's own, andbun scripts/rename.tscovers the same variants for a later rename. The turbo generator smoke test restoresbun.lock, sobun run cileaves the lockfile untouched.