chore(repo): add dev:fresh script (wipes Next caches before starting)#21
Merged
Conversation
After heavy branch-switching, PR merges, or installs touching apps/, the running Next dev servers can lose track of their webpack module graph and start returning 404 for every /_next/static/* chunk. Hit this three times in one calibration session. dev:fresh removes apps/*/.next and apps/*/.turbo before running pnpm dev so a session that starts with this command is guaranteed a clean Next build. Standard `pnpm dev` is unchanged for users who want to keep an existing cache.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
pnpm dev:freshthat wipesapps/*/.nextandapps/*/.turbobefore runningpnpm dev. Standardpnpm devis unchanged.Why
Hit Next.js dev-cache corruption three times in one calibration session. Root cause: heavy branch switching and PR merges leave the running Next dev servers with a stale in-memory module graph; webpack-runtime can't find chunks; every
/_next/static/*returns 404 and the page won't render. Symptom is always the sameCannot find module './<N>.js'error.The fix has been the same three times: kill the dev servers,
rm -rf .next, restart. Now it's one command.Test plan
pnpm typecheck- 9/9 workspaces pass (no code changes, just a script)pnpm check- cleanpnpm build- cleanMoat level
L1 - developer ergonomics, not product. Reduces the friction of a known recurring issue.