Shared Removal Loop

Vuesion is a foundation, not a finished product. Every guide in this section lists what to delete to remove one optional feature. No refactoring is needed.

Removal guides never change Vuesion itself. They only describe what you delete in your own project.

Before you start

Work on a branch.

The baseline must be green: npm run lint, npm test and npm run build pass before you delete anything. Otherwise you cannot tell your own errors from existing ones.

The loop

• Delete the entry points listed in the guide.
• Run npm run lint:code. Fix every reported error by deleting the dead reference.
• Handle everything under "Not found by the compiler" in the guide: runtime config strings, env variables, i18n keys, Prisma schema and migrations, and docs links. The i18n extractor (npm run extract-i18n-messages) only adds keys and never removes unused ones, so delete them by hand from the files in i18n/locales, including the -server files.
• Run npm test. The 100% coverage threshold exposes code that became dead. Delete it and its tests, and never lower thresholds.
• Run npm run build.
• Repeat until lint, test and build pass.

Database

Removing a Prisma model needs a new migration. Create it with npm run db:migrate.

Never edit or delete existing migrations. A database reset needs your explicit confirmation.

Anatomy of a guide

Every guide has three sections.

• Entry points lists the files, directories, env variables, config keys and other starting points to delete. A test in the repository verifies that every listed path exists.
• Not found by the compiler lists the references that lint, tests and build do not report. You find these by hand.
• Coding-agent prompt holds a ready-made prompt for a coding agent.

Using a coding agent

Each guide ends with a prompt. Give the agent the guide and this page, and let it run the loop.