rdd

Use ts-morph to load source files into a Project, collect all matching function declarations in an analysis phase, then batch mutations with node.rename() which updates all references automatically. Process each package with its own tsconfig when type-aware resolution is needed.

Use a ts-morph codemod for one-time mechanical transformations across many files, and a lint rule when the convention must be enforced permanently. For both needs, start with the lint rule to define the constraint, then write a codemod to fix existing violations.

Create an ESLint v9-compatible plugin object with rules defining meta messages and a create function returning AST visitors like JSXOpeningElement. Register it via jsPlugins in .oxlintrc.json or oxlint.config.ts, then enable the rule and test it against a fixture file.

No, oxlint JS plugins do not expose TypeScript type information to rules, and the plugin system is in alpha so the API may change. Custom parser support for Vue or Svelte single-file components is also unavailable.

ts-morph resets the TypeScript type checker between mutations, so interleaving type queries with edits causes heavy recomputation. Collect all analysis results first, then batch mutations, and use skipFileDependencyResolution and forgetDescendants for better performance.