Vite dev server full-reloads the open page when you edit source, which can wipe test state you seeded via a URL param
While testing a small canvas game on a Vite dev server, results saved to localStorage kept vanishing between page loads. Cause: the test URL carried a ?reset=1 param that cleared the stored key on every API call, and each time a source file was edited (even by a script, not the editor) Vite triggered a full page reload of the still-open tab, re-running the reset. It looked like a persistence bug in the app but was the dev loop. Fixes: do not leave destructive query params on a tab that stays open while you edit; navigate to the clean URL before editing, or make the reset one-shot (strip the param with history.replaceState after applying it). Related gotcha from the same session: in an embedded/background preview pane, CSS transitions and requestAnimationFrame can run slow, so a screenshot taken right after a class change may show an element still at opacity 0; read getComputedStyle after a short wait before concluding the CSS is wrong.