chore(site): how we built vercle functions blog

[NathanFlurry]

No description provided.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-site	Ready	Preview	Comment	Oct 20, 2025 1:48pm

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-cloud	Ignored			Oct 20, 2025 1:48pm
rivet-inspector	Ignored	Preview		Oct 20, 2025 1:48pm

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

[NathanFlurry]

• chore(site): how we built vercle functions blog #3228 👈 (View in Graphite)
• 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.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/rivet-dev/engine/@rivetkit/engine-runner@3228

npm i https://pkg.pr.new/rivet-dev/engine/@rivetkit/engine-runner-protocol@3228

commit: e154351

[claude]

PR Review: Blog Post - WebSocket Servers for Vercel Functions

Overview

This PR adds a comprehensive technical blog post explaining how Rivet enables WebSocket servers on Vercel Functions using tunneling. The content is well-written, technically accurate, and provides excellent educational value.

---

✅ Strengths

Content Quality

• Excellent technical depth: The tunneling explanation is clear, well-illustrated, and accessible to both beginners and experienced developers
• Strong narrative structure: Progresses logically from problem to solution to implementation details to future work
• Great use of diagrams: Visual aids effectively illustrate complex networking concepts
• Practical code examples: Both raw WebSocket and high-level API examples are clear and functional
• Comprehensive FAQ section: Addresses common questions like SSE alternatives and why Vercel doesn't natively support WebSockets

Technical Accuracy

• Correctly describes the tunneling architecture and how it solves serverless limitations
• Accurate explanation of actor lifecycle, state management, and fault tolerance
• Proper context on Vercel's edge network and multi-region support

---

🔍 Issues & Recommendations

1. Typo in PR Title (Critical)

The PR title says "vercle" instead of "vercel"

Action: Update the PR title

2. WebSocket Cleanup Missing (Medium Priority)

Lines 131-152: The WebSocket connection is never closed when the component unmounts. Consider adding cleanup logic to close the WebSocket in the useEffect return function.

3. Missing Error Handling (Medium Priority)

Lines 132-151, 227-229: Code examples lack error handling for WebSocket connection failures, JSON parse errors, and network timeouts. Consider adding try-catch blocks or comments indicating error handling should be added in production.

4. TypeScript Type Safety (Low Priority)

Lines 125, 220: Messages state is initialized as empty array without type annotation. Consider adding explicit types for better TypeScript safety.

---

📝 Version Bump

The version bump from 25.8.0 to 25.8.1 across all packages in Cargo.lock and openapi.json looks correct and follows semantic versioning conventions for a content-only release.

---

🎯 Summary

Overall Assessment: Excellent blog post with minor issues

Required Changes:

1. Fix typo in PR title: "vercle" to "vercel"

Recommended Changes:

1. Add WebSocket cleanup in useEffect
2. Add error handling examples or comments
3. Add TypeScript type annotations for better safety

---

🚀 Great Work!

This is a high-quality technical blog post that:

• Clearly explains a complex architectural pattern
• Provides practical, working code examples
• Addresses common concerns and alternatives
• Will serve as excellent documentation for the community

The issues identified are relatively minor and mostly focused on making the code examples more production-ready. The core content is solid and ready to publish with minimal changes.

Approval Status: ✅ Approved with minor recommendations

---

Review generated by Claude Code