feat(example): hono + bun

[jog1t]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rivetkit-serverless	Ready	Preview	Comment	Oct 7, 2025 9:21pm

[claude]

Claude finished @jog1t's task —— View job

---

Code Review for Hono + Bun Example

I've completed a comprehensive review of the new Hono + Bun example. Here's my analysis:

Todo List:

• Read project guidelines from CLAUDE.md
• Analyze all files in the new hono-bun example
• Compare with existing examples for consistency
• Review code quality and best practices
• Check for potential bugs and security issues
• Assess performance considerations
• Evaluate test coverage
• Provide comprehensive feedback

✅ Positive Aspects

1. Project Structure & Guidelines Compliance

• Correctly follows the expected example structure from CLAUDE.md
• turbo.json properly extends from root configuration
• package.json follows naming convention (example-hono-bun)
• Uses workspace:* for RivetKit dependency as required
• Keywords appropriately included

2. Code Quality

• Clean, readable TypeScript code
• Proper use of RivetKit actor pattern in registry.ts
• Good separation of concerns between registry and server logic
• TypeScript configuration aligns with project standards

3. Integration Implementation

• Demonstrates proper Hono + Bun integration with RivetKit
• Correctly uses Bun-specific WebSocket upgrade functionality
• Shows both HTTP and WebSocket endpoint examples

⚠️ Issues Found

1. README.md Guideline Violations

• Installation instructions inconsistent: README shows npm install but this is a Bun example - should be bun install
• Development command mismatch: README shows npm run dev but should be bun run dev for consistency

2. Package.json Issues

• Missing keywords: The example lacks some keywords present in similar examples like "web", "framework", "runtime"
• Script inconsistency: Uses tsx --watch pattern in hono example but bun --watch here - this is actually correct but worth noting the intentional difference

3. Code Quality Concerns

• Missing error handling: server.ts:20-23 - No error handling around actor operations
• Console.log usage: Lines 32, 36, 54 use console.log instead of the recommended logger() pattern from CLAUDE.md
• WebSocket implementation: Basic WebSocket example doesn't demonstrate RivetKit integration

4. Security & Performance

• No input validation: /increment/:name endpoint doesn't validate the name parameter
• Potential DoS: No rate limiting on actor creation via getOrCreate(name)
• WebSocket security: No authentication or origin validation

5. Missing Features

• No test coverage: No tests provided (common across examples but worth noting)
• No client script: Unlike the regular hono example which has a client script
• Limited WebSocket demo: WebSocket doesn't integrate with RivetKit actors

🔧 Specific Recommendations

High Priority:

1. Fix README installation commands: Change npm install to bun install and npm run dev to bun run dev
2. Replace console.log: Use logger() pattern as per CLAUDE.md guidelines
3. Add basic input validation: Validate actor names to prevent potential issues

Medium Priority:

1. Add error handling: Wrap actor operations in try-catch blocks
2. Enhance WebSocket example: Show RivetKit actor integration in WebSocket handler
3. Add missing keywords: Include "web", "framework", "runtime" keywords

Low Priority:

1. Consider adding a client script: Like the regular hono example for testing
2. Add JSDoc comments: For public-facing functions as recommended in guidelines

🏁 Overall Assessment

This is a solid example that successfully demonstrates Hono + Bun integration with RivetKit. The code is clean and functional, but has some guideline compliance issues and missing best practices. The implementation correctly showcases the key differences from the Node.js Hono example (using Bun runtime, Bun WebSocket APIs, and Bun.serve).

Recommendation: ✅ Approve with minor changes - The issues found are not blocking and can be addressed in follow-up improvements.

---

[jog1t]

• feat(example): hono + bun #1358 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merge queue - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[pkg-pr-new]

More templates

• example-ai-agent
• example-better-auth-external-db
• chat-room
• example-cloudflare-workers
• example-cloudflare-workers-hono
• example-counter
• example-counter-serverless
• example-crdt
• example-database
• example-deno
• example-sqlite
• example-elysia
• example-express
• example-game
• example-hono
• example-hono-bun
• example-hono-react
• example-kitchen-sink
• example-next-js
• example-rate
• example-raw-fetch-handler
• example-raw-websocket-handler-proxy
• example-react
• starter
• example-stream
• example-sync
• example-tenant
• example-trpc

@rivetkit/actor

pnpm add https://pkg.pr.new/rivet-dev/rivetkit/@rivetkit/actor@1358

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivetkit/@rivetkit/cloudflare-workers@1358

@rivetkit/core

pnpm add https://pkg.pr.new/rivet-dev/rivetkit/@rivetkit/core@1358

@rivetkit/db

pnpm add https://pkg.pr.new/rivet-dev/rivetkit/@rivetkit/db@1358

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivetkit/@rivetkit/framework-base@1358

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivetkit/@rivetkit/next-js@1358

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivetkit/@rivetkit/react@1358

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivetkit@1358

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivetkit/@rivetkit/sql-loader@1358

commit: 1b59059

[claude]

Claude finished @jog1t's task —— View job

---

Code Review for Hono + Bun Example

I've completed a comprehensive review of the new Hono + Bun example. Here's my analysis:

Todo List:

• Read project guidelines from CLAUDE.md
• Analyze all files in the new hono-bun example
• Compare with existing examples for consistency
• Review code quality and best practices
• Check for potential bugs and security issues
• Assess performance considerations
• Evaluate test coverage
• Provide comprehensive feedback

✅ Positive Aspects

1. Project Structure & Guidelines Compliance

• Correctly follows the expected example structure from CLAUDE.md
• turbo.json properly extends from root configuration
• package.json follows naming convention (example-hono-bun)
• Uses workspace:* for RivetKit dependency as required
• Keywords appropriately included

2. Code Quality

• Clean, readable TypeScript code
• Proper use of RivetKit actor pattern in registry.ts:3-15
• Good separation of concerns between registry and server logic
• TypeScript configuration aligns with project standards

3. Integration Implementation

• Demonstrates proper Hono + Bun integration with RivetKit
• Correctly uses Bun-specific WebSocket upgrade functionality (server.ts:2,12)
• Shows both HTTP and WebSocket endpoint examples

⚠️ Issues Found

1. README.md Guideline Violations

• Installation instructions inconsistent: README.md:20 shows npm install but this is a Bun example - should be bun install
• Development command mismatch: README.md:26 shows npm run dev but should be bun run dev for consistency

2. Package.json Issues

• Missing keywords: The example lacks some keywords present in similar examples like "web", "framework", "runtime"
• Script inconsistency: Uses bun --watch pattern in this example vs tsx --watch in regular hono example - this is actually correct but worth noting the intentional difference

3. Code Quality Concerns

• Missing error handling: server.ts:23-29 - No error handling around actor operations
• Console.log usage: server.ts:38,42,54 use console.log instead of the recommended logger() pattern from CLAUDE.md:102-105
• WebSocket implementation: Basic WebSocket example doesn't demonstrate RivetKit integration

4. Security & Performance

• No input validation: /increment/:name endpoint (server.ts:23-24) doesn't validate the name parameter
• Potential DoS: No rate limiting on actor creation via getOrCreate(name)
• WebSocket security: No authentication or origin validation

5. Missing Features

• No test coverage: No tests provided (common across examples but worth noting)
• Limited client script: Unlike the regular hono example which has a client script, this one has connect.ts but it's not referenced in package.json
• Limited WebSocket demo: WebSocket doesn't integrate with RivetKit actors

🔧 Specific Recommendations

High Priority:

1. Fix README installation commands: Change npm install to bun install and npm run dev to bun run dev
2. Replace console.log: Use logger() pattern as per CLAUDE.md guidelines
3. Add basic input validation: Validate actor names to prevent potential issues

Medium Priority:

1. Add error handling: Wrap actor operations in try-catch blocks
2. Enhance WebSocket example: Show RivetKit actor integration in WebSocket handler
3. Add missing keywords: Include "web", "framework", "runtime" keywords
4. Add client script: Reference the connect script in package.json like other examples

Low Priority:

1. Add JSDoc comments: For public-facing functions as recommended in guidelines
2. Consider WebSocket authentication: For production readiness

🏁 Overall Assessment

This is a solid example that successfully demonstrates Hono + Bun integration with RivetKit. The code is clean and functional, but has some guideline compliance issues and missing best practices. The implementation correctly showcases the key differences from the Node.js Hono example (using Bun runtime, Bun WebSocket APIs, and Bun.serve).

Recommendation: ✅ Approve with minor changes - The issues found are not blocking and can be addressed in follow-up improvements.

---

[claude]

Claude finished @jog1t's task —— View job

---

Code Review for Hono + Bun Example

I've completed a comprehensive review of the new Hono + Bun example. Here's my analysis:

Todo List:

• Read project guidelines from CLAUDE.md
• Analyze all files in the new hono-bun example
• Compare with existing examples for consistency
• Review code quality and best practices
• Check for potential bugs and security issues
• Assess performance considerations
• Evaluate test coverage
• Provide comprehensive feedback

✅ Positive Aspects

1. Project Structure & Guidelines Compliance

• Correctly follows the expected example structure from CLAUDE.md
• turbo.json properly extends from root configuration
• package.json follows naming convention (example-hono-bun)
• Uses workspace:* for RivetKit dependency as required
• Keywords appropriately included

2. Code Quality

• Clean, readable TypeScript code
• Proper use of RivetKit actor pattern in registry.ts
• Good separation of concerns between registry and server logic
• TypeScript configuration aligns with project standards

3. Integration Implementation

• Demonstrates proper Hono + Bun integration with RivetKit
• Correctly uses Bun-specific WebSocket upgrade functionality
• Shows both HTTP and WebSocket endpoint examples

⚠️ Issues Found

1. README.md Guideline Violations

• Installation instructions inconsistent: README shows npm install but this is a Bun example - should be bun install
• Development command mismatch: README shows npm run dev but should be bun run dev for consistency

2. Package.json Issues

• Missing keywords: The example lacks some keywords present in similar examples like "web", "framework", "runtime"
• Script inconsistency: Uses tsx --watch pattern in hono example but bun --watch here - this is actually correct but worth noting the intentional difference

3. Code Quality Concerns

• Missing error handling: server.ts:20-23 - No error handling around actor operations
• Console.log usage: Lines 32, 36, 54 use console.log instead of the recommended logger() pattern from CLAUDE.md
• WebSocket implementation: Basic WebSocket example doesn't demonstrate RivetKit integration

4. Security & Performance

• No input validation: /increment/:name endpoint doesn't validate the name parameter
• Potential DoS: No rate limiting on actor creation via getOrCreate(name)
• WebSocket security: No authentication or origin validation

5. Missing Features

• No test coverage: No tests provided (common across examples but worth noting)
• No client script: Unlike the regular hono example which has a client script
• Limited WebSocket demo: WebSocket doesn't integrate with RivetKit actors

🔧 Specific Recommendations

High Priority:

1. Fix README installation commands: Change npm install to bun install and npm run dev to bun run dev
2. Replace console.log: Use logger() pattern as per CLAUDE.md guidelines
3. Add basic input validation: Validate actor names to prevent potential issues

Medium Priority:

1. Add error handling: Wrap actor operations in try-catch blocks
2. Enhance WebSocket example: Show RivetKit actor integration in WebSocket handler
3. Add missing keywords: Include "web", "framework", "runtime" keywords

Low Priority:

1. Consider adding a client script: Like the regular hono example for testing
2. Add JSDoc comments: For public-facing functions as recommended in guidelines

🏁 Overall Assessment

This is a solid example that successfully demonstrates Hono + Bun integration with RivetKit. The code is clean and functional, but has some guideline compliance issues and missing best practices. The implementation correctly showcases the key differences from the Node.js Hono example (using Bun runtime, Bun WebSocket APIs, and Bun.serve).

Recommendation: ✅ Approve with minor changes - The issues found are not blocking and can be addressed in follow-up improvements.

---

[claude]

Claude finished @jog1t's task —— View job

---

Code Review for Hono + Bun Example

I've completed a comprehensive review of the new Hono + Bun example. Here's my analysis:

Todo List:

• Read project guidelines from CLAUDE.md
• Analyze all files in the new hono-bun example
• Compare with existing examples for consistency
• Review code quality and best practices
• Check for potential bugs and security issues
• Assess performance considerations
• Evaluate test coverage
• Provide comprehensive feedback

✅ Positive Aspects

1. Project Structure & Guidelines Compliance

• Correctly follows the expected example structure from CLAUDE.md
• turbo.json properly extends from root configuration
• package.json follows naming convention (example-hono-bun)
• Uses workspace:* for RivetKit dependency as required
• Keywords appropriately included

2. Code Quality

• Clean, readable TypeScript code
• Proper use of RivetKit actor pattern in registry.ts:3-15
• Good separation of concerns between registry and server logic
• TypeScript configuration aligns with project standards

3. Integration Implementation

• Demonstrates proper Hono + Bun integration with RivetKit
• Correctly uses Bun-specific WebSocket upgrade functionality (server.ts:2,12)
• Shows both HTTP and WebSocket endpoint examples

⚠️ Issues Found

1. README.md Guideline Violations

• Installation instructions inconsistent: README.md:20 shows npm install but this is a Bun example - should be bun install
• Development command mismatch: README.md:26 shows npm run dev but should be bun run dev for consistency

2. Package.json Issues

• Missing keywords: The example lacks some keywords present in similar examples like "web", "framework", "runtime"
• Script inconsistency: Uses bun --watch pattern in this example vs tsx --watch in regular hono example - this is actually correct but worth noting the intentional difference

3. Code Quality Concerns

• Missing error handling: server.ts:23-29 - No error handling around actor operations
• Console.log usage: server.ts:38 uses console.log instead of the recommended logger() pattern from CLAUDE.md:102-105
• WebSocket implementation: Basic WebSocket example doesn't demonstrate RivetKit integration

4. Security & Performance

• No input validation: /increment/:name endpoint (server.ts:23-24) doesn't validate the name parameter
• Potential DoS: No rate limiting on actor creation via getOrCreate(name)
• WebSocket security: No authentication or origin validation

5. Missing Features

• No test coverage: No tests provided (common across examples but worth noting)
• Client script inconsistency: Has connect.ts but not referenced in package.json scripts like the regular hono example's client script
• Limited WebSocket demo: WebSocket doesn't integrate with RivetKit actors

🔧 Specific Recommendations

High Priority:

1. Fix README installation commands: Change npm install to bun install and npm run dev to bun run dev
2. Replace console.log: Use logger() pattern as per CLAUDE.md guidelines
3. Add basic input validation: Validate actor names to prevent potential issues

Medium Priority:

1. Add error handling: Wrap actor operations in try-catch blocks
2. Enhance WebSocket example: Show RivetKit actor integration in WebSocket handler
3. Add missing keywords: Include "web", "framework", "runtime" keywords
4. Add client script: Reference the connect script in package.json like other examples

Low Priority:

1. Add JSDoc comments: For public-facing functions as recommended in guidelines
2. Consider WebSocket authentication: For production readiness

🏁 Overall Assessment

This is a solid example that successfully demonstrates Hono + Bun integration with RivetKit. The code is clean and functional, but has some guideline compliance issues and missing best practices. The implementation correctly showcases the key differences from the Node.js Hono example (using Bun runtime, Bun WebSocket APIs, and Bun.serve).

Recommendation: ✅ Approve with minor changes - The issues found are not blocking and can be addressed in follow-up improvements.

---

[graphite-app]

Merge activity

• Oct 7, 8:48 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Oct 7, 8:49 PM UTC: CI is running for this pull request on a draft pull request (#1362) due to your merge queue CI optimization settings.
• Oct 7, 8:50 PM UTC: Merged by the Graphite merge queue via draft PR: #1362.