Repository navigation
v2.0.0
Major Changes
-
#42
b364e99Thanks @stevensacks! - React Router relaxations move out ofreactinto a new opt-inreactRouterblock.reactshipped a block scoped to**/routes/**/*.tsxthat turnedno-empty-patternoff. That glob is not unique to React Router: TanStack Router uses aroutes/directory too, so a project on any other file-based router had the rule silently disabled across its whole route tree, with nothing in the composed config explaining why.The relaxation now ships as its own block. Spread it after
reactif you run React Router in framework mode:...lint.react, ...lint.reactRouter,
Breaking for React Router consumers. Without that line,
no-empty-patternreports every route module that destructures nothing from its typed props (({}: Route.ComponentProps)). Adding the spread restores the previous behavior exactly; there is no other migration step. A project that never writes that shape sees no new errors either way, so the upgrade may well be a no-op in practice.Projects on another router should omit it and keep the rule enabled. They will most likely also want to ignore their generated route tree:
...lint.ignores({extra: ['**/routeTree.gen.ts']}),
The
/.react-router/**glob stays in theignoresdefaults. It names a directory that only exists in a React Router project, so it costs other projects nothing, while moving it would break React Router consumers who miss the new spread.A new suite asks ESLint what the composed config resolves to on both sides of the opt-in, so a future change that folds the block back into
react, or widens its glob, fails a test instead of quietly relaxing a rule.Two dead config entries are removed in the same pass. Neither changes any effective rule:
react/display-namewas set tooffin the route block, butairbnb/config/reactalready sets it toofffor every file.- The
typescript/only-throw-errorblock disabled@typescript-eslint/only-throw-errorforhooks/,routes/, andsessions.server/, but thetypescript/configblock already disables that rule globally for**/*.ts?(x).