${count}
` ``) is flagged,\n since it renders the function once and never updates; a property that doesn't exist on an\n inferred param is reported.\n- **Quiet where it should be** — unused-component reports and implicit-`any` noise on params\n the template can infer are dropped.\n- **Quick fixes** — \"Call `count`\" for a bare accessor, with a fix-all for the file.\n\n## Enable it\n\nAdd it to your project's `tsconfig.json` and use the **workspace** TypeScript version\n(VS Code: `TypeScript: Select TypeScript Version → Use Workspace Version` — tsconfig plugins\nonly load under the workspace TS):\n\n```jsonc\n{\n \"compilerOptions\": {\n \"plugins\": [{ \"name\": \"@fluixi/ts-plugin\" }]\n }\n}\n```\n\nNothing else. JSX needs no plugin, and neither do the `$signal`-style intrinsics — those are\ntyped by the `fluixi.d.ts` the compiler generates.\n\n## How it stays out of the way\n\nEverything is computed on the **existing** program's checker. The plugin creates no language\nservice, adds no files, and never touches the host — it wraps the service it's handed, and\nevery addition is wrapped so a failure costs the extra information, never the real answer.\n\nThat restraint is deliberate. Two earlier designs for deep type-checking inside `${…}` holes\nboth had to go: a second `ts.LanguageService` meant a second document registry, so lib.d.ts\nand node_modules were parsed twice; and shadow files added via `getScriptFileNames` re-entered\nhost machinery on every project sync and crashed the language service outright. Hole\ndiagnostics weren't worth either — a `${…}` hole is a real expression, so TypeScript already\nchecks it.\n\n## License\n\nMIT\n","readmeFilename":"README.md"}