fix(rivetkit): prevent Turbopack from tracing sqlite-vfs dynamic import

[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

[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

• 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 👈 (View in Graphite)
• 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.

[railway-app]

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

Service	Status	Web	Updated (UTC)
frontend-cloud	😴 Sleeping (View Logs)	Web	Mar 25, 2026 at 7:46 am
website	😴 Sleeping (View Logs)	Web	Mar 24, 2026 at 5:39 pm
frontend-inspector	😴 Sleeping (View Logs)	Web	Mar 24, 2026 at 11:46 am
kitchen-sink	❌ Build Failed (View Logs)	Web	Mar 24, 2026 at 11:34 am
ladle	❌ Build Failed (View Logs)	Web	Mar 24, 2026 at 2:01 am
mcp-hub	✅ Success (View Logs)	Web	Mar 24, 2026 at 1:58 am

[claude]

PR Review: fix(rivetkit) prevent Turbopack from tracing sqlite-vfs dynamic import

Summary

The fix is correct and the approach is a well-known workaround for bundlers that statically analyze dynamic import strings. Overall this is a good minimal change.

---

Issues

Inline type annotation is verbose and duplicates existing type

The type annotation on line 31 is a very long one-liner that is hard to read. Worse, the return shape of SqliteVfsPool (acquire and shutdown) is already captured in the poolPromise field type at lines 9-13. These two definitions can drift silently. Consider extracting named local types SqliteVfsPoolInstance and SqliteVfsPoolCtor to avoid duplication, then reuse SqliteVfsPoolInstance in the field type too.

Webpack and other bundlers may warn on computed specifier

Webpack and other bundlers that perform static analysis of import() expressions will emit a warning when the specifier is not a string literal. This is usually just a warning and not a breakage, but worth validating that existing webpack/esbuild consumers do not regress.

---

Nits

• The import type at line 1 is a type-only import, which TypeScript/bundlers strip at compile time, so it will not cause Turbopack to trace into the module graph. This is fine as-is.
• No linked upstream Turbopack issue in the PR description. If one exists, linking it would help future readers understand when this workaround can be reverted.

---

Verdict

Approve with the suggestion to extract the inline type to improve readability and prevent future drift. The core fix is correct.