eslint-plugin-remix-react-routes
eslint-plugin-remix-react-routes copied to clipboard
jenseng
Validate routes referenced by <Link> and friends in a Remix app
If I try to make use of this with remix v2.3.1 I get this: ``` npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While...
Example code: [email protected] **Expected Behavior:** Does not throw an eslint error **Actual Behavior:** Throws an eslint error
As of 1.12.0, remix (and react-router) [can handle absolute URLs](https://github.com/remix-run/remix/blob/remix%401.12.0/packages/remix-react/CHANGELOG.md#1120) in ``s, so this is no longer worth linting. We should detect the Remix version and emit a warning if...
I was having a peer dependency warning even though everything was working perfectly. I'm on `2.0.1` but thought `^2.1.0` would be good enough. Feel free to make any changes!
Thanks for this package! Can't believe I've waited this long to try it. My package.json is `type: module` so I'd like to keep my remix.config.js with the .js extension. Right...
Not everything is auto-fixable, but it would be nice to support it for at least the following rules: * **use-link-for-routes** - switch to remix equivalents * `` -> `` *...
Currently the rules evaluate paths in relation to the route containing the element, as is the case with `` by default at runtime; i.e. consider a route hierarchy like so:...
Currently the [RemixContext](https://github.com/jenseng/eslint-plugin-remix-react-routes/blob/main/src/remixContext.ts) determines whether or not we're in a route at the file level. This is fine if the `` usage happens within the default route component, but potentially...