Code Components fail with “Component file does not exist” — even a new minimal component fails
Hi! I’m experiencing what appears to be a Code Component runtime/module-loading issue in one Framer project.
All existing Code Components suddenly stopped rendering and now show:
Error in local-module:codeFile...default — Component file does not exist.
I performed diagnostics through Framer’s external agent APIs.
Verified:
• All 9 original .tsx Code Component files still exist and are readable. • Their source matches saved pre-failure backups. • Framer detects a valid default component export from every file. • Strict CodeFile typechecking returns zero TypeScript diagnostics for all files. • All 30 canvas component references across desktop, tablet and mobile point to the correct existing CodeFile IDs/exports. • No missing or mismatched CodeFile IDs were found. • The same issue occurs in Chrome Incognito. • Older Page Version History snapshots show the same errors.
I then created a completely new, minimal RuntimeTest.tsx component containing only simple React text and inline styling. It has no dependency on my portfolio code, images, Motion, external packages or project assets.
The new component fails too with:
Component file does not exist
even though Framer detects its default export and it passes typecheck.
Preview console reports:
[CodeGenerationStore] TypeError: Failed to fetch
along with source-cache/dependency-module loading failures.
This seems to indicate a Code Component module loading/registration problem affecting this project rather than an error in an individual component.
Has anyone encountered this, or know how to make Framer rebuild/re-register the project’s Code Component modules without deleting/recreating the existing components and canvas instances?
I can provide CodeFile IDs, screenshots, exact console errors and additional diagnostic information if needed.
Framer team/expert: I’m happy to provide a remix/project link privately if needed.
