New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
8 recipes · 47 steps · about 39 minutes of reading
A full browser reload on every save, instead of the instant update Vite promised.
You read import.meta.env.VITE_API_URL and get undefined, even though the value sits right there in your .env file.
You have an index.html and an about.html. Only index.html ever lands in the shipped build output.
Everything works with npm run preview, then every asset 404s the moment the site goes live on GitHub Pages.
Calling a real backend from your dev server throws a CORS error the moment you stop pointing fetch at fake local data.
A user has your app open when you ship a new deploy. One click throws an error for a chunk that no longer exists, and the screen goes blank.
Vite's build warns that your main chunk is over 500 kB, and the whole app downloads before a single page renders.
Why does the dev server die on startup the moment a teammate opens your repo inside a container?
Cookbook badge
Finish all 8 recipes to earn this.