This guide helps you reset your Tuturuuu repository to a clean state, which is
useful if you encounter dependency issues or want to ensure a fresh
development environment.
1.4.4 (official release).
Keep active workspace metadata and CI pins aligned with the root packageManager.
Change manifest metadata with bun pm pkg set packageManager=bun@1.4.4 in each
owning workspace. An updated pin does not upgrade an installed host or runner;
verify bun --version separately. Retained paused runtime files and historical
reproduction notes keep their original versions.
Prerequisites
- Ensure you have bun installed. The repository pins a specific
Bun version via the
packageManagerfield in the rootpackage.json(currentlybun@1.4.4) — match that version so your local toolchain stays in sync. - Use the Node.js version pinned in the root
.node-version(currently26.12.1). The rootenginesfield keeps a>=22.13.0support floor; see Node.js runtime pin.
Quick Cleanup (Recommended)
The repository ships a one-shot root script that performs the full cleanup for you:bun.lock, deletes every node_modules directory, and clears all
.next and .turbo build caches across the monorepo (it uses
npkill --delete-all under the hood). After it finishes, reinstall everything:
Manual Cleanup (Granular Alternative)
1. Delete the lockfile
Remove thebun.lock file at the root of your repository (if it exists):
2. Remove all node_modules folders
Use npkill to find and remove all node_modules directories:
- In the
npkillinterface, select and delete allnode_modulesfolders found in your repo.
3. Clear build caches (optional)
Remove stale.next and .turbo build caches if you suspect they are causing
issues (the bun clean shortcut does this automatically):
4. Reinstall dependencies
Install all required dependencies using bun:After completing these steps, your repository should be in a clean state. You
can now continue with the usual development workflow as described in
Development.
Troubleshooting
- If you still encounter issues, try restarting your IDE or terminal.
- Make sure your bun version is up to date:
bun upgrade. - If problems persist, check the Development guide or ask for help in the project discussions.