Revert "fix(rivetkit): gate node:sqlite behind RIVETKIT_NODE_SQLITE env var"

[NathanFlurry]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[railway-app]

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

Service	Status	Web	Updated (UTC)
kitchen-sink	❌ Build Failed (View Logs)	Web	Mar 26, 2026 at 9:07 am
frontend-inspector	❌ Build Failed (View Logs)	Web	Mar 26, 2026 at 8:18 am
frontend-cloud	❌ Build Failed (View Logs)	Web	Mar 26, 2026 at 8:18 am
website	😴 Sleeping (View Logs)	Web	Mar 25, 2026 at 4:54 pm
ladle	❌ Build Failed (View Logs)	Web	Mar 25, 2026 at 4:44 pm
mcp-hub	✅ Success (View Logs)	Web	Mar 25, 2026 at 4:42 pm

[NathanFlurry]

• Revert "fix(rivetkit): gate node:sqlite behind RIVETKIT_NODE_SQLITE env var" #4508 👈 (View in Graphite)
• fix: correct stop codes #4507
• feat(sandbox): add test counter and SQLite load actors #4500
• chore: actor epoxy scoped consensus #4502
• fix(rivetkit): copy Buffer to Uint8Array in ensureUint8Array to fix .slice() semantics #4506 : 1 other dependent PR (#4510 )
• fix(rivetkit): setup database before lifecycle hooks for c.db availability #4494
• fix(rivetkit): remove drizzle-orm peer dep and add runtime version check #4492
• chore(skill): add version check to rivetkit skill #4491
• fix(rivetkit): prevent Turbopack from tracing sqlite-vfs dynamic import #4490
• fix(rivetkit): warn when manager port falls back to a different port #4489
• fix(rivetkit): clear connectableTs on actor sleep #4488
• fix(rivetkit): gate node:sqlite behind RIVETKIT_NODE_SQLITE env var #4487
• main

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

[claude]

PR Review: Revert node:sqlite env var gate\n\n### Summary\n\nThis revert removes the RIVETKIT_NODE_SQLITE=1 opt-in gate and unconditionally attempts node:sqlite, while also removing the better-sqlite3 package as an explicit dependency.\n\n### Concerns\n\n1. Noisy experimental warning returns\n\nThe original fix suppressed the Node.js ExperimentalWarning: SQLite is an experimental feature and might change at any time that fires for all users on Node 22.x. This revert brings that warning back.\n\nIf the motivation is that node:sqlite graduated to stable in Node 23.4+, that is a valid reason but Node 22 is still the active LTS and users on it will see this warning on every actor startup. It would help to document the rationale in the PR description.\n\nOne middle ground worth considering: check the Node.js major/minor version and only use node:sqlite on 23.4+ (where it is stable), falling through to better-sqlite3 on older releases.\n\n2. better-sqlite3 removed from deps but still referenced in code\n\nbetter-sqlite3 was removed from package.json dependencies, but sqlite-runtime.ts lines 152-181 still try to load it as a fallback, and the runtime kind enum on line 3 still includes better-sqlite3. The fallback still works at runtime (the error message tells users to install it manually), but users on Node 22 who hit that path will encounter an unexplained failure unless they read the error carefully. This is a behavior regression compared to before the original fix.\n\n3. Empty PR description\n\nThe default PR template was not filled in. Since this is a revert of a deliberate fix (the original PR comment explained the tradeoff in detail), it would be helpful to explain why the original fix is being reverted.\n\n### Minor\n\nThe ensureUint8Array comment on line 212 still references from better-sqlite3 - accurate since it can still be loaded at runtime, just not bundled as an explicit dep. Fine as-is.\n\n### Verdict\n\nThe change itself is clean and minimal. The main risk is the regression of experimental warnings for Node 22 LTS users, combined with better-sqlite3 no longer being a bundled fallback. Clarifying the intent and Node version support expectations before merging would be helpful.

[pkg-pr-new]

More templates

• actor-actions
• actor-actions-vercel
• ai-agent
• ai-agent-vercel
• example-ai-and-user-generated-actors-freestyle
• chat-room
• chat-room-vercel
• example-cloudflare-workers
• example-cloudflare-workers-hono
• collaborative-document
• collaborative-document-vercel
• cross-actor-actions
• cross-actor-actions-vercel
• example-cursors
• example-cursors-raw-websocket
• example-cursors-raw-websocket-vercel
• example-cursors-vercel
• custom-serverless
• example-elysia
• example-experimental-durable-streams-ai-agent
• example-experimental-durable-streams-ai-agent-vercel
• geo-distributed-database
• geo-distributed-database-vercel
• hello-world
• hello-world-vercel
• example-hono
• hono-react
• hono-react-vercel
• example-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• example-multiplayer-game-patterns
• example-multiplayer-game-patterns-vercel
• multiplayer-game-vercel
• native-websockets
• native-websockets-vercel
• next-js
• per-tenant-database
• per-tenant-database-vercel
• example-raw-fetch-handler
• example-raw-fetch-handler-vercel
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-raw-websocket-handler-proxy-vercel
• example-raw-websocket-handler-vercel
• example-react
• example-react-vercel
• sandbox
• sandbox-coding-agent
• sandbox-coding-agent-vercel
• sandbox-vercel
• scheduling
• scheduling-vercel
• example-sqlite-drizzle
• example-sqlite-raw
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc

@rivetkit/cloudflare-workers

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

@rivetkit/framework-base

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

@rivetkit/next-js

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

@rivetkit/react

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

rivetkit

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

@rivetkit/sql-loader

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

@rivetkit/sqlite-vfs

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sqlite-vfs@4508

@rivetkit/traces

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

@rivetkit/workflow-engine

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/workflow-engine@4508

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@4508

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@4508

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@4508

commit: 1a02e25

[NathanFlurry]

Merge activity

• Mar 25, 7:43 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Mar 25, 8:13 PM UTC: Graphite couldn't merge this pull request because a downstack PR fix: correct stop codes #4507 failed to merge.
• Mar 26, 9:05 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Mar 26, 9:07 AM UTC: Graphite rebased this pull request as part of a merge.
• Mar 26, 9:07 AM UTC: @NathanFlurry merged this pull request with Graphite.