chore(next-js): enable fluid

[NathanFlurry]

No description provided.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
rivetkit-next-js-max	Ready	Preview	Comment	Oct 18, 2025 7:03am
rivetkit-serverless	Ready	Preview	Comment	Oct 18, 2025 7:03am

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

[claude]

Claude finished @NathanFlurry's task —— View job

---

Code Review: chore(next-js): enable fluid

Todo List:

• Analyze the deleted vercel.json file and its purpose
• Check the next-js example directory structure
• Review impact on deployment configuration
• Assess security, performance, and functionality implications
• Provide comprehensive review feedback

Review Summary

This PR removes the vercel.json file that explicitly disabled Vercel's "fluid" deployment mode. The change is minimal but has deployment implications.

Code Quality & Best Practices ✅

• Clean change: Simple file deletion with clear intent
• Follows semantic versioning: Uses chore: prefix appropriately
• Minimal scope: Only affects deployment configuration, no code changes

Potential Issues & Considerations ⚠️

Missing Context:

• No PR description: The PR lacks explanation of why fluid mode is being enabled
• No documentation update: The README.md still contains generic Next.js boilerplate and doesn't reflect RivetKit-specific deployment considerations

Deployment Impact:

• Fluid mode changes: Enabling Vercel's fluid mode may affect:
  • Build performance and caching behavior
  • Cold start times
  • Resource allocation
  • Edge function distribution

Performance Considerations 🚀

• Potential improvement: Fluid mode typically provides better performance through optimized edge distribution
• Unknown impact: Without testing, it's unclear how this affects the RivetKit Next.js example specifically

Security Concerns 🔒

• Low risk: Removing deployment configuration doesn't introduce security vulnerabilities
• Configuration exposure: Default Vercel behavior will now apply instead of explicit opt-out

Test Coverage 🧪

• No tests affected: This is purely a deployment configuration change
• Manual testing recommended: The deployment should be verified on Vercel to ensure the example still works correctly

Recommendations

1. Add PR description explaining why fluid mode is being enabled
2. Update README.md to follow RivetKit standards (see CLAUDE.md guidelines for examples)
3. Consider documentation about deployment implications if this affects user experience
4. Test deployment to ensure the example functions correctly with fluid mode enabled

Overall Assessment

✅ Approved with suggestions

This is a safe, focused change that modernizes the deployment configuration. The missing context and documentation updates are minor issues that can be addressed in follow-up work.

---

[NathanFlurry]

• chore(next-js): enable fluid #1404 👈 (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-background-jobs
• example-better-auth-external-db
• example-bots
• 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-freestyle
• 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
• example-raw-websocket-handler-proxy
• example-react
• example-smoke-test
• starter
• example-stream
• example-sync
• example-tenant
• example-trpc
• example-workflows

@rivetkit/actor

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

@rivetkit/cloudflare-workers

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

@rivetkit/core

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

@rivetkit/db

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

@rivetkit/framework-base

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

@rivetkit/next-js

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

@rivetkit/react

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

rivetkit

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

@rivetkit/sql-loader

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

commit: ee3c0ff

[claude]

Claude finished @NathanFlurry's task —— View job

---

Pull Request Review: chore(next-js): enable fluid

Todo List:

• Analyze the deleted vercel.json file and its purpose
• Review the config.ts changes
• Check the next-js example directory structure for context
• Assess impact on deployment configuration
• Evaluate security, performance, and functionality implications
• Provide comprehensive review feedback

Review Summary

This PR makes two changes:

1. Removes vercel.json from examples/next-js/ that explicitly disabled Vercel's "fluid" deployment mode
2. Reduces sleepTimeout in packages/rivetkit/src/actor/config.ts:72 from 30,000ms to 15,000ms

Code Quality & Best Practices ✅

Positive aspects:

• Clean, minimal changes: Simple file deletion and single-line modification with clear intent
• Semantic commit: Uses appropriate chore: prefix for infrastructure changes
• Focused scope: Changes are targeted and don't introduce unnecessary complexity

Areas for improvement:

• Missing PR description: No explanation provided for why fluid mode is being enabled
• Documentation gap: The README.md still contains generic Next.js boilerplate and doesn't reflect RivetKit-specific deployment considerations (violates CLAUDE.md guidelines)

Potential Issues & Considerations ⚠️

Vercel.json removal (examples/next-js/vercel.json):

• Previous config: {"fluid": false} explicitly opted out of Vercel's fluid mode
• New behavior: Default Vercel behavior will now apply (fluid mode enabled)
• Risk assessment: Low risk change, but impact should be tested

Sleep timeout reduction (packages/rivetkit/src/actor/config.ts:72):

• Change: sleepTimeout reduced from 30,000ms (30s) to 15,000ms (15s)
• Scope: Affects all actor configurations that don't explicitly override this default
• Potential impact: More aggressive actor sleeping behavior may affect performance characteristics
• Missing context: No explanation for why this change was bundled with the Vercel fluid enablement

Performance Considerations 🚀

Vercel Fluid Mode:

• Potential benefits:
  • Better edge distribution and caching
  • Improved cold start performance
  • Enhanced global performance
• Unknown impacts: Without testing, unclear how this affects RivetKit-specific functionality

Actor Sleep Timeout:

• Performance trade-off: Shorter timeout means:
  • ✅ Faster resource cleanup and potentially lower costs
  • ⚠️ More frequent cold starts for intermittent workloads
  • ⚠️ Potential impact on user experience for chatroom-style applications

Security Concerns 🔒

• Low security risk: Configuration changes don't introduce vulnerabilities
• Deployment behavior: Default Vercel settings will now apply instead of explicit opt-out

Test Coverage 🧪

• No tests affected: These are infrastructure/configuration changes
• Manual testing needed:
  • Verify Next.js example deploys correctly with fluid mode
  • Test actor behavior with reduced sleep timeout
  • Validate chatroom functionality still works as expected

Recommendations

1. Add PR description explaining:

   • Why fluid mode is being enabled
   • Why sleep timeout is being reduced
   • If these changes are related or should be separate commits

2. Update documentation:

   • examples/next-js/README.md should follow RivetKit standards per CLAUDE.md guidelines
   • Consider documenting deployment implications if they affect user experience

3. Consider separation of concerns:

   • The sleep timeout change affects core actor behavior globally
   • Should this be a separate commit/PR from the Vercel-specific change?

4. Testing validation:

   • Deploy and test the example to ensure fluid mode works correctly
   • Monitor for any behavioral changes with the reduced sleep timeout

Overall Assessment

✅ Approved with suggestions

This is a safe, focused change that modernizes the deployment configuration. The missing context and documentation are minor issues that can be addressed in follow-up work. The sleep timeout reduction should be monitored for any unexpected behavioral changes.

The code changes themselves are clean and follow good practices, though they would benefit from better documentation and separation of concerns.

[claude]

Claude finished @NathanFlurry's task —— View job

---

Pull Request Review: chore(next-js): enable fluid

Todo List:

• Read repository guidelines (CLAUDE.md)
• Analyze deleted vercel.json file and its purpose
• Review changes to route.ts file
• Review changes to config.ts file
• Assess code quality and best practices
• Identify potential bugs or issues
• Evaluate performance considerations
• Check security concerns
• Assess test coverage impact
• Provide comprehensive review feedback

---

Review Summary

This PR makes three changes:

1. Removes vercel.json that explicitly disabled Vercel's "fluid" deployment mode
2. Increases maxDuration in Next.js route from 60s to 300s (5 minutes)
3. Reduces sleepTimeout in actor config from 30,000ms to 15,000ms

Code Quality & Best Practices ✅

Positive aspects:

• Clean, minimal changes: Targeted modifications with clear intent
• Semantic commit: Uses appropriate chore: prefix for infrastructure changes
• Consistent code style: Changes follow existing patterns

Areas for improvement:

• Missing PR description: No explanation for why these changes are bundled together
• Documentation gap: The examples/next-js/README.md still contains generic Next.js boilerplate, violating CLAUDE.md guidelines for examples (lines 153-192)
• Mixed concerns: Three unrelated changes bundled in one commit

Potential Issues & Considerations ⚠️

Vercel.json removal (examples/next-js/vercel.json):

• Previous: {"fluid": false} explicitly opted out of Vercel's fluid mode
• Now: Default Vercel behavior applies (fluid mode enabled)
• Impact: Changes deployment behavior for better edge distribution

maxDuration increase (examples/next-js/src/app/api/rivet/[...all]/route.ts:4):

• Previous: 60 seconds timeout
• Now: 300 seconds (5 minutes) timeout
• Justification: Reasonable for long-running actor operations
• Consistency: Aligns with Vercel's 5-minute serverless function limit

sleepTimeout reduction (packages/rivetkit/src/actor/config.ts:72):

• Previous: 30,000ms (30 seconds)
• Now: 15,000ms (15 seconds)
• Scope: Affects ALL actor configurations globally
• Trade-off: Faster resource cleanup vs. more frequent cold starts

Performance Considerations 🚀

Vercel Fluid Mode:

• ✅ Benefits: Improved edge distribution, better caching, enhanced global performance
• ⚠️ Unknown impact: Need to verify RivetKit-specific functionality works correctly

Timeout Changes:

• ✅ maxDuration increase: Allows longer-running operations, reducing timeout errors
• ⚠️ sleepTimeout reduction: More aggressive cleanup may increase cold start frequency
• Consideration: Monitor for performance impact on chatroom-style applications

Security Concerns 🔒

• Low risk: Configuration changes don't introduce security vulnerabilities
• Deployment behavior: Default Vercel settings now apply instead of explicit opt-out

Test Coverage 🧪

• No tests affected: These are infrastructure/configuration changes
• Manual testing needed:
  • Verify Next.js example deploys correctly with fluid mode
  • Test actor behavior with reduced sleep timeout and increased max duration
  • Validate long-running operations don't timeout prematurely

Documentation Issues 📚

README.md compliance: The examples/next-js/README.md doesn't follow CLAUDE.md standards and should include:

• RivetKit-specific title format
• Project description mentioning RivetKit
• Standard RivetKit links and structure
• RivetKit-specific installation/development instructions

Recommendations

1. Separate concerns: Consider splitting into separate commits:

   • Vercel fluid enablement
   • Next.js timeout adjustments
   • Actor config changes

2. Add context: Provide PR description explaining:

   • Why fluid mode is being enabled
   • Rationale for timeout adjustments
   • Expected impact on performance

3. Update documentation:

   • Fix examples/next-js/README.md to follow CLAUDE.md guidelines
   • Consider documenting deployment implications

4. Monitor deployment: Test the example to ensure fluid mode works correctly with RivetKit

Overall Assessment

✅ Approved with suggestions

This is a well-intentioned change that modernizes the deployment configuration and adjusts timeouts for better performance. The changes themselves are safe and technically sound. The main issues are around documentation standards and commit organization rather than functional concerns.

The code quality is good and the changes follow RivetKit's technical standards, though they would benefit from better documentation and clearer separation of concerns.

---

[claude]

Claude finished @NathanFlurry's task —— View job

---

Pull Request Review: chore(next-js): enable fluid

Todo List:

• Read repository guidelines (CLAUDE.md)
• Examine the deleted vercel.json file and understand its purpose
• Review the route.ts changes
• Analyze the next-js example structure for context
• Assess code quality and best practices
• Evaluate security implications
• Review performance considerations
• Check test coverage impact
• Provide comprehensive review feedback

Review Summary

This PR makes two distinct changes:

1. Removes vercel.json from examples/next-js/ that explicitly disabled Vercel's "fluid" deployment mode ({"fluid": false})
2. Increases maxDuration in examples/next-js/src/app/api/rivet/[...all]/route.ts:4 from 60 seconds to 300 seconds (5 minutes)

Code Quality & Best Practices ✅

Positive aspects:

• Clean, minimal changes: Simple file deletion and single-line modification
• Semantic commit: Uses appropriate chore: prefix for infrastructure changes
• Valid TypeScript: The route.ts modification is syntactically correct
• Follows Next.js patterns: The maxDuration export is a standard Next.js route configuration

Areas for improvement:

• Missing PR description: No explanation for why these changes are being made together
• Documentation gap: The README.md violates CLAUDE.md guidelines - it still contains generic Next.js boilerplate instead of following the required RivetKit example structure (lines 153-192 in CLAUDE.md)
• Separation of concerns: Two unrelated changes bundled in one commit

Potential Issues & Considerations ⚠️

Vercel.json removal:

• Previous behavior: Explicitly opted out of Vercel's fluid mode
• New behavior: Default Vercel behavior (fluid mode enabled)
• Impact: May affect deployment performance, edge distribution, and caching behavior
• Risk: Low, but deployment behavior will change

maxDuration increase (60s → 300s):

• Scope: Affects all HTTP methods (GET, POST, PUT, PATCH, HEAD, OPTIONS) for the RivetKit API routes
• Context: This example implements a chat room with persistent actors
• Justification: Longer-running operations may be necessary for actor lifecycle management
• Concern: No explanation provided for why 5 minutes is needed

Performance Considerations 🚀

Fluid Mode (Vercel.json removal):

• Potential benefits:
  • Improved edge distribution and performance
  • Better caching strategies
  • Enhanced global latency
• Unknown impacts: Testing needed to verify chatroom functionality still works correctly

Increased maxDuration:

• Trade-offs:
  • ✅ Allows longer-running actor operations without timeout
  • ⚠️ May increase resource usage and costs
  • ⚠️ Could mask performance issues in actor implementations
• Context relevance: For a chatroom example with persistent actors, longer durations may be appropriate for state synchronization

Security Concerns 🔒

• Low security risk: Configuration changes don't introduce vulnerabilities
• Resource exhaustion: 5-minute timeout could potentially be exploited for resource exhaustion, but this is mitigated by Vercel's platform limits
• No sensitive data exposure: Changes don't affect data handling or authentication

Test Coverage 🧪

• No test files affected: These are infrastructure/configuration changes
• Manual testing required:
  • Verify Next.js example deploys correctly with fluid mode enabled
  • Test chatroom functionality with increased timeout duration
  • Validate WebSocket connections and actor persistence still work

Compliance with Repository Guidelines 📋

Violations of CLAUDE.md:

• README.md format: The examples/next-js/README.md doesn't follow the required structure (CLAUDE.md lines 153-192)
• Missing RivetKit branding: Should be titled "Next.js Chat Room for RivetKit"
• Missing required links: Discord, documentation, and issues links are absent
• Generic content: Still contains Next.js boilerplate instead of RivetKit-specific instructions

Recommendations

1. Add PR description explaining:

   • Why fluid mode is being enabled
   • Why maxDuration is being increased to 5 minutes
   • Whether these changes are related or coincidental

2. Fix documentation compliance:

   • Update examples/next-js/README.md to follow CLAUDE.md guidelines
   • Include proper RivetKit branding and links
   • Add specific instructions for the chatroom example

3. Consider separation:

   • These appear to be unrelated changes that could be separate commits
   • Vercel deployment optimization vs. Next.js route timeout configuration

4. Testing validation:

   • Deploy and test the example to ensure fluid mode works correctly
   • Verify 5-minute timeout doesn't cause issues with typical chatroom usage

Overall Assessment

✅ Approved with suggestions

The technical changes are sound and appear beneficial for the chatroom example. The increased timeout makes sense for persistent actor operations, and enabling fluid mode should improve deployment performance. However, the PR would benefit from better documentation and explanation of the changes.

The code itself is clean and follows good practices, though the repository documentation needs updating to comply with project standards.

---

[claude]

Claude finished @NathanFlurry's task —— View job

---

Pull Request Review: chore(next-js): enable fluid

Todo List:

• Read repository guidelines (CLAUDE.md)
• Analyze the changed files in detail
• Review code quality and best practices
• Identify potential bugs or issues
• Evaluate performance considerations
• Check security concerns
• Assess test coverage impact
• Provide comprehensive review feedback

---

Review Summary

This PR makes three distinct changes:

1. Removes vercel.json that explicitly disabled Vercel's "fluid" deployment mode
2. Increases maxDuration in Next.js route from 60s to 300s (5 minutes)
3. Adds serverless configuration in the Next.js package with explicit runner limits and request lifespan

Code Quality & Best Practices ✅

Positive aspects:

• Clean, targeted changes: Modifications are focused and purposeful
• Semantic commit: Uses appropriate chore: prefix for infrastructure changes
• Consistent TypeScript: All changes follow existing code patterns
• Logical configuration: The serverless config aligns with the increased route timeout (both 300s)

Areas for improvement:

• Missing PR description: No explanation for bundling these related but distinct changes
• Documentation violation: examples/next-js/README.md:1-37 violates CLAUDE.md guidelines - it contains generic Next.js boilerplate instead of the required RivetKit example structure

Potential Issues & Considerations ⚠️

Vercel.json removal (examples/next-js/vercel.json):

• Previous: {"fluid": false} explicitly opted out of Vercel's fluid mode
• Now: Default Vercel behavior applies (fluid mode enabled)
• Impact: Changes deployment behavior for better edge distribution and performance

Route timeout increase (examples/next-js/src/app/api/rivet/[...all]/route.ts:4):

• Change: maxDuration increased from 60s to 300s (5 minutes)
• Scope: Affects all HTTP methods for RivetKit API routes
• Justification: Aligns with Vercel's serverless function limit and supports long-running actor operations

Serverless configuration (packages/next-js/src/mod.ts:32-35):

• New config: Adds explicit minRunners, maxRunners, requestLifespan, and slotsPerRunner
• Values: minRunners: 0, maxRunners: 100_000, requestLifespan: 300, slotsPerRunner: 1
• Consistency: requestLifespan: 300 matches the route maxDuration: 300

Performance Considerations 🚀

Vercel Fluid Mode Benefits:

• ✅ Improved edge distribution: Better global performance
• ✅ Enhanced caching: More efficient resource utilization
• ✅ Optimized cold starts: Faster initial response times

Timeout and Configuration Changes:

• ✅ Longer request handling: 5-minute limit supports complex actor operations
• ✅ Explicit resource limits: maxRunners: 100_000 provides clear scaling boundaries
• ✅ Minimal resource footprint: minRunners: 0 allows scaling to zero
• ⚠️ Potential cost implications: Longer-running requests may increase serverless costs

Security Concerns 🔒

Low Risk Assessment:

• No vulnerabilities introduced: Configuration changes don't expose security issues
• Resource limits: maxRunners: 100_000 provides protection against runaway scaling
• Timeout boundaries: 5-minute limit prevents indefinite resource consumption

Test Coverage 🧪

No Direct Impact:

• Configuration changes: These modifications don't affect existing test logic
• Manual testing needed:
  • Verify Next.js example deploys correctly with fluid mode
  • Test actor operations within the 5-minute timeout window
  • Validate serverless scaling behavior with new configuration

Compliance Issues 📋

CLAUDE.md Violations:

• README.md format: examples/next-js/README.md doesn't follow required structure (CLAUDE.md lines 155-192)
• Missing RivetKit branding: Should use "Next.js Chat Room for RivetKit" format
• Generic content: Contains Next.js boilerplate instead of RivetKit-specific instructions

Code-Specific Observations

examples/next-js/src/app/api/rivet/[...all]/route.ts:4

export const maxDuration = 300; // Increased from 60

✅ Good: Aligns with Vercel limits and serverless configuration

packages/next-js/src/mod.ts:32-35

autoConfigureServerless = {
  url: `${publicUrl}/api/rivet`,
  minRunners: 0,        // New: allows scaling to zero
  maxRunners: 100_000,  // New: sets upper limit
  requestLifespan: 300, // New: matches route timeout
  slotsPerRunner: 1,    // New: explicit slot configuration
};

✅ Good: Comprehensive serverless configuration
✅ Good: Consistent timeout values across the stack

Recommendations

1. Add PR description explaining the relationship between these changes and why they're bundled together

2. Fix documentation compliance:

   • Update examples/next-js/README.md to follow CLAUDE.md guidelines
   • Include proper RivetKit branding and structure

3. Consider monitoring:

   • Track deployment performance with fluid mode enabled
   • Monitor serverless costs with longer request durations

4. Testing validation:

   • Deploy and verify the example works correctly with all changes
   • Test edge cases near the 5-minute timeout limit

Overall Assessment

✅ Approved

This is a well-coordinated set of changes that modernizes the Next.js example's deployment configuration. The changes are technically sound and logically consistent:

• Enabling fluid mode should improve deployment performance
• The 5-minute timeout provides adequate headroom for actor operations
• The explicit serverless configuration adds clarity and control

The code quality is excellent and follows RivetKit's technical standards. The primary issue is documentation compliance, which can be addressed in a follow-up.

---