Treat LiteFS helpers as local when disabled#804
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthrough
ChangesLiteFS conditional wrapper layer
Blog list MDX cache TTL
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
litefs-jswrapper calls as local no-ops unlessLITEFS_ENABLED=true..primary, emitting Fly replay headers, waiting on tx-number files, or replaying requests to a primary instance that no longer exists.Testing
npm --workspace kentcdodds.com run typecheckpassed.npm --workspace kentcdodds.com run test:backendpassed.PORT=4300,MOCKS=true,LITEFS_ENABLED=falsereturned/healthcheckin ~1ms and/build/info.jsonwithX-Fly-Primary-Instance: local-no-litefs.git pushpre-push hook remains blocked by missing Playwright Chromium in this Cloud VM; pushed withHUSKY=0after explicit focused checks.Summary by CodeRabbit
New Features
Chores