chore(examples): update examples to standardized format

[NathanFlurry]

No description provided.

[railway-app]

🚅 Deployed to the rivet-pr-3799 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
frontend-cloud-staging	❌ Build Failed (View Logs)	Web	Jan 9, 2026 at 9:24 pm
website	❌ Build Failed (View Logs)	Web	Jan 9, 2026 at 9:23 pm
frontend-inspector	🕐 Queued (View Logs)	Web	Jan 9, 2026 at 9:23 pm
frontend-cloud	🕐 Queued (View Logs)	Web	Jan 9, 2026 at 9:22 pm

---

🚅 Deployed to the rivet-pr-3799 environment in rivet-frontend-website-preview

Service	Status	Web	Updated (UTC)
frontend-cloud	◻️ Removed (View Logs)		Jan 9, 2026 at 5:01 pm

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• chore(rivetkit): update cloudflare workers and nextjs to latest #3803
• chore(examples): update examples to standardized format #3799 👈 (View in Graphite)
• chore(example): update examples to use srvx #3790
• chore(examples): add node server dependency #3788
• Update examples to serverless format #3785
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

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.

[claude]

PR Review: #3799 - Update examples to standardized format

Overview

This PR implements a comprehensive standardization effort across all examples in the repository. The changes are primarily structural and configurational, establishing consistent patterns for project structure, configuration files, naming conventions, and documentation.

Overall Assessment: ✅ Approve with minor suggestions

This is excellent work that will significantly improve the maintainability and consistency of the examples. The standardization is thorough and well-documented.

---

Key Strengths

1. Comprehensive Documentation ✅

• Added examples/CLAUDE.md with detailed guidelines for example structure
• Added .claude/resources/EXAMPLE_TEMPLATE.md for README standardization
• Clear section headings and requirements for all examples

2. Consistent Configuration ✅

• Standardized tsconfig.json with ESM support (allowImportingTsExtensions, rewriteRelativeImportExtensions)
• Unified package.json structure with metadata (template field with technologies, tags, frontendPort)
• Added vercel.json to all examples for proper Hono framework detection

3. File Naming Convention ✅

• Renamed src/registry.ts → src/actors.ts across all examples
• Consistent import pattern: import { registry } from "./actors.ts" with explicit .ts extension

4. Build & Dev Scripts Standardization ✅

• Clear distinction between examples with frontend, separate servers, and backend-only
• Consistent script names: dev, dev:backend, dev:frontend, build, check-types, test

5. Cleanup ✅

• Removed redundant examples (chat-room-next-js, deno, express)
• All examples now follow a clear pattern

---

Issues Found

🔴 Critical: Inconsistent Package Naming

Location: Multiple package.json files across examples

Issue: Package names are inconsistent. Some use example- prefix while others do not:

• ✅ example-ai-agent, example-elysia, example-hono, example-sqlite (drizzle)
• ❌ actor-actions, chat-room, cursors, cursors-raw-websocket, cross-actor-actions

Expected: All examples should follow example-{name} format for consistency.

Recommendation:

# These should be renamed in their package.json files:
"actor-actions" → "example-actor-actions"
"chat-room" → "example-chat-room"
"cursors" → "example-cursors"
"cursors-raw-websocket" → "example-cursors-raw-websocket"
"cross-actor-actions" → "example-cross-actor-actions"
# etc.

Files to fix:

• examples/actor-actions/package.json:2
• examples/chat-room/package.json:2
• examples/cursors/package.json:2
• examples/cursors-raw-websocket/package.json:2
• examples/cross-actor-actions/package.json:2
• examples/custom-serverless/package.json:2
• examples/ai-and-user-generated-actors-freestyle/package.json:2

---

⚠️ Medium: Drizzle Example Server is Commented Out

Location: examples/drizzle/src/server.ts:1-7

Issue: The entire server implementation is commented out:

// import { Hono } from "hono";
// import { registry } from "./actors.ts";
//
// const app = new Hono();
// app.all("/api/rivet/*", (c) => registry.handler(c.req.raw));
// export default app;

Impact: This example will not run. The package.json has scripts pointing to src/server.ts, but the file exports nothing.

Recommendation: Either:

1. Uncomment the server code if it should be a standard example
2. Add a comment explaining why it is commented
3. Update the README to explain this is a code reference only

---

⚠️ Medium: Inconsistent stableVersion Placement

Location: Various package.json files

Issue: The stableVersion field appears inconsistently:

• Some examples have it (e.g., drizzle/package.json:28, elysia/package.json:24)
• Some examples do not have it at all (e.g., actor-actions/package.json)

Recommendation: Either add stableVersion to all examples consistently, or document why only some examples have it.

---

⚠️ Medium: Inconsistent TSConfig Comments

Location: Various tsconfig.json files

Issue:

• Some examples have detailed comments explaining each option (e.g., actor-actions/tsconfig.json, drizzle/tsconfig.json)
• Others are minimal without comments (e.g., elysia/tsconfig.json)

Recommendation: Choose one style consistently. The examples/CLAUDE.md documentation does not specify which to use.

---

⚠️ Medium: Extra Field in drizzle/tsconfig.json

Location: examples/drizzle/tsconfig.json:11

Issue: The drizzle example has "allowArbitraryExtensions": true which is not present in other examples.

Question: Is this intentional for Drizzle-specific needs, or was it accidentally left in?

Recommendation: Either document why Drizzle needs this in a comment, or remove it if not needed.

---

💡 Minor: Elysia Example Uses Elysia Framework

Location: examples/elysia/src/server.ts

Observation: The Elysia example uses Elysia native framework instead of Hono, but still declares "framework": "hono" in vercel.json.

Question: Is Vercel properly handling Elysia with the Hono framework declaration? This might work but seems semantically incorrect.

Recommendation: Test deployment to Vercel or add a comment explaining this intentional configuration.

---

💡 Minor: Missing Frontend Include in Some tsconfig.json

Location: examples/actor-actions/tsconfig.json:44

Issue: The include array is ["src/**/*", "tests/**/*"] but there is a frontend/ directory with TypeScript files.

Impact: Frontend TypeScript files may not get type-checked by check-types script.

Recommendation: Update to "include": ["src/**/*", "frontend/**/*", "tests/**/*"] for examples with frontend code.

---

Best Practices Observations

✅ Security: Good Dependency Practices

• Using workspace references for internal packages ("rivetkit": "*")
• Proper version pinning for external dependencies
• "private": true" prevents accidental npm publication

✅ Type Safety

• All examples use "strict": true"
• TypeScript 5.5.2 for latest features
• Proper isolatedModules for bundler compatibility

✅ Code Quality

• Consistent import patterns with explicit .ts extensions (ESM-compliant)
• No actual logic changes, just structural improvements
• Clean separation of concerns (actors, server, frontend)

---

Testing Considerations

💡 Suggestion: Test the Standardization

To ensure nothing broke, recommend running:

# For each example
cd examples/actor-actions
pnpm install
pnpm build
pnpm test (if tests exist)
pnpm dev (manually verify it starts)

Especially important for:

• drizzle (commented server)
• elysia (different framework)
• Examples with frontend (ensure proxy works)

---

Summary of Recommendations

Must Fix Before Merge:

1. ✅ Standardize package names - All should use example- prefix
2. ✅ Fix or document drizzle commented server - Currently broken
3. ✅ Audit and fix stableVersion field - Should be consistent

Should Fix Before Merge:

4. ⚠️ Standardize tsconfig.json comment style - Document preferred style
5. ⚠️ Review drizzle allowArbitraryExtensions - Document or remove
6. ⚠️ Add frontend to tsconfig include - For examples with frontend/

Nice to Have:

7. 💡 Verify Elysia + Vercel deployment - Ensure it works as expected
8. 💡 Test all examples - Ensure nothing broke

---

Conclusion

This is a high-quality PR that significantly improves the codebase organization. The standardization effort is thorough and well-thought-out. The main issues are minor inconsistencies that should be addressed for completeness.

Recommendation: Request changes to address the critical naming inconsistency and the broken drizzle example, then merge after verification.

Great work! 🎉

[vercel]

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

Project	Deployment	Review	Updated (UTC)
rivet-cloud	Error		Jan 9, 2026 9:22pm
rivetkit-serverless	Error		Jan 9, 2026 9:22pm

2 Skipped Deployments

Project	Deployment	Review	Updated (UTC)
rivet-inspector	Ignored	Preview	Jan 9, 2026 9:22pm
rivet-site	Ignored	Preview	Jan 9, 2026 9:22pm

[graphite-app]

Merge activity

• Jan 9, 9:23 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Jan 9, 9:23 PM UTC: CI is running for this pull request on a draft pull request (#3804) due to your merge queue CI optimization settings.
• Jan 9, 9:24 PM UTC: Merged by the Graphite merge queue via draft PR: #3804.