eslint-plugin-no-relative-import-paths
eslint-plugin-no-relative-import-paths copied to clipboard
MelvinVermeer
Hi! 👋 Firstly, thanks for your work on this project! 🙂 Today I used [patch-package](https://github.com/ds300/patch-package) to patch `[email protected]` for the project I'm working on. Here is the diff that solved...
I use some kind of fractal design pattern plus atomic design for my apps and usually it is pretty normal to have imports one or two folders up like `'../MyComponent'`...
implements the work done by @richard-lopes-ifood here https://github.com/MelvinVermeer/eslint-plugin-no-relative-import-paths/issues/12 Works flawlessly as far as I can see
Hi, love this plugin! I like the option `rootDir`, would it be possible to add another option keep the `rootDir` in the import if the import terminates with a direct...
Add Support for inline imports ```js const Test = React.lazy(() => import("../../Test")) ``` Template: [import-js/eslint-plugin-import](https://github.com/import-js/eslint-plugin-import/blob/main/utils/moduleVisitor.js)
Hi @MelvinVermeer and thanks for the useful plugin! The problem: We use ESLint's auto-fixing in IDEs to run after each save. Unfortunately, we've got multiple aliases setup in `tsconfig.json` and...
Hey, first of all, thanks for the great plugin! What do you think about having an `allowParentFolder` option to allow `'../Component'` imports? It could be particularly useful in tests (e.g....
Config: ```json "no-relative-import-paths/no-relative-import-paths": [ "error", { "allowSameFolder": true } ] ``` Catches the following: `../path/to/relative/parent/import` But not: `./../path/to/relative/parent/import`
In my project I'm having issues formating "export" lines. It works normally in imports.  My eslint config: 
In my TypeScript project, strangely it only works for type imports:  My ESLint configuration:  I thought it might be a conflict with the "unused-imports"...
