v1.0.0 — TypeScript 7 ready, and it's about time
react-router-auto-routes migrator CLI no longer depends on the TypeScript compiler API. TypeScript 7 (the native Go compiler) does not expose the old programmatic API, so the migration CLI's AST parsing has moved to oxc-parser. You can now run your project on TypeScript 7 — or remove TypeScript 5/6 from your environment entirely — and everything keeps working. The typescript peer dependency is gone.
Beyond that, this release makes official what has been true for a while: the library has been stable in production, the API hasn't changed since 0.8.0, and every issue reported along the way has been resolved.
Breaking
- Node.js requirement is now
^20.19.0 || >=22.12.0(required byoxc-parser).
Migration CLI
- The CLI now fails fast instead of writing partial output:
- Files with syntax errors abort the migration before anything is written (all files are validated up front; a failure means zero writes).
- Route entries whose
flatRoutes/createRoutesFromFoldersoptions reference local variables (including shorthand properties) abort with instructions to inline the values. - Aliased legacy imports (e.g.
import { flatRoutes as fr }) abort instead of silently generating a bareautoRoutes()entry.
- Added
--help/-h; unknown flags are now errors instead of being treated as directory names. - Parse errors include the file name, Oxc diagnostics, and how to fix them.
Internal
- Import specifier rewrites now preserve
?url/#hashsuffixes and no longer mid-string-match unrelated paths (e.g.~/lib/routes/foo-utils).