Prune migration notes and align the notes with the current lint setup

2026-10-16 23:41:04 +09:00
parent 662e946fad
commit 15fe481181
12 changed files with 47 additions and 174 deletions
@@ -11,11 +11,15 @@ Oxlint plugin with `meta.name` `"project"`, loaded through `jsPlugins` in
  plugin configs: Deno parity rules, extras, per-rule options, and opt-outs,
  built-in Oxlint ids included (`curly`, `id-match`, `import/no-cycle`, ...).
 - **Custom rules**, enabled as `project/<rule>`. Every repo has
-  `no-disable-comments` and `no-non-ts-imports`. Apps also port the rules of
+  `no-disable-comments` and `no-asset-imports`. Apps also port the rules of
  their old `scripts/deno-lint-plugin.ts` here under the same names and
  behavior (`no-self-sync`, `app-module-conventions`, `restricted-types`, ...).

-Rules and plugin stay in this one file; don't add `scripts/rules/`.
+`scripts/` stays flat; don't add `scripts/rules/`. A file that would pass
+`max-lines` (300) splits into flat themed files sharing the prefix:
+`scripts/project-lint.ts` keeps the plugin object and the rule list and
+imports the others (`project-lint-modules.ts`, `project-lint-types.ts`,
+`project-lint-lit.ts`, ...).

 ```ts
 import type { DummyRuleMap } from "vite-plus/lint";