drop the dev tagger plugin: the compiler already annotates, and this one did not exist

The dependency was an unrelated package that happens to share a plausible name,
pinned to a version that was never published, so --frozen-lockfile 404'd and
neither install nor build ran at all. Importing it at the top of vite.config.ts
meant the config itself could not load.

Nothing is lost by deleting rather than replacing it. The gui compiler emits the
same annotation from the AST pass that already walks every component, gated on
NODE_ENV=development: data-is (which component), data-in (the component it is
used inside) and data-at (file:line). It runs AFTER flattening, so the tag names
the component that actually rendered rather than one the optimizer removed.

Co-authored-by: Hanzo Dev <[email protected]>

package.json

@@ -86,7 +86,6 @@
     "eslint-plugin-react-hooks": "^5.1.0-rc.0",
     "eslint-plugin-react-refresh": "^0.4.9",
     "globals": "^15.9.0",
-    "component-tagger": "^1.1.3",
     "postcss": "^8.4.47",
     "tailwindcss": "^4.0.17",
     "typescript": "^5.5.3",

vite.config.ts

@@ -1,7 +1,6 @@
 import { defineConfig } from "vite";
 import react from "@vitejs/plugin-react-swc";
 import path from "path";
-import { componentTagger } from "component-tagger";
 
 // https://vitejs.dev/config/
 export default defineConfig({
@@ -11,8 +10,6 @@ export default defineConfig({
   },
   plugins: [
     react(),
-    // Only include componentTagger in development mode
-    process.env.NODE_ENV === 'development' && componentTagger(),
   ].filter(Boolean),
   resolve: {
     alias: {