SolidJS & SolidStart App Build Cache (.solid)

Bottom Line: It is 100% safe to delete .solid and dist directories. SolidJS automatically regenerates clean reactive component bundles on your next npm run dev or npm run build.

Why Does SolidJS Build Cache Exist?

SolidJS compiles fine-grained reactive JSX components into vanilla DOM operations. SolidStart uses Vinxi and Vite to cache route bundles inside .solid/ and dist/.

• Primary Purpose: Intermediate compilation of reactive JSX templates and SSR route manifests.
• Storage Impact: Consumes 300 MB to 3 GB of local workspace storage.

What Happens If You Delete SolidJS Cache?

• System Safety: ✅ 100% Safe to Delete. Original .tsx source code is untouched.
• Automatic Regeneration: Running npx solid-start build re-compiles clean assets.
• Reclaimed Storage: Frees 300 MB to 3 GB of storage space.

How to Delete SolidJS Cache

# Delete SolidJS build output and cache
rm -rf .solid dist .output node_modules/.vite

Frequently Asked Questions (FAQ)

Does SolidJS use Virtual DOM?

No. SolidJS compiles templates directly to real DOM nodes, which is why deleting build caches forces a clean re-compilation of DOM templates.