Skip to content

test(rsc): add persistent use cache example - #1411

Draft
hi-ogawa wants to merge 16 commits into
mainfrom
fix/issue-1409
Draft

test(rsc): add persistent use cache example#1411
hi-ogawa wants to merge 16 commits into
mainfrom
fix/issue-1409

Conversation

@hi-ogawa

@hi-ogawa hi-ogawa commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

TODO

The existing use cache examples keep entries in function-keyed memory, which naturally loses them when a transformed module is reevaluated and does not expose persistent-cache invalidation requirements.

This PR adds a standalone file-level use cache example with a filesystem-backed handler and self-contained Flight values. A development module generation and reverse-importer hotUpdate traversal invalidate entries after cached function, direct dependency, and transitive dependency edits.

hi-ogawa and others added 11 commits August 6, 2026 16:05
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
@hi-ogawa hi-ogawa changed the title feat(rsc): add persistent use cache example test(rsc): add persistent use cache example Aug 6, 2026
hi-ogawa and others added 5 commits August 6, 2026 18:00
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add use cache example with external persistence beyond in-memory store Research "use cache" cache invalidation strategy during dev

1 participant