Current plugin is just about force use aliases instead of relative paths (and back for deprecated aliases).
If you need to sort imports, you may try rule simple-import-sort/imports from https://github.com/lydell/eslint-plugin-simple-import-sort
It is very flexible, so you may customize your own groups. For instance, you may group aliases in one group and relative imports to another group. Check their docs
Sorry, maybe I’m not being clear - I’m not talking about sorting. I’m talking about an ESLint rule that flags alias imports that can be expressed as relative subdirectory imports, but flags other imports that could have been alias imports. Does that make sense?
Examples:
// we're in @/lib/foo// correctimport A from"./foobar/a"import B from"./b"import C from"@/lib/c"import D from"@/d"// incorrectimport A from"@/lib/foo/foobar/a"import B from"@/lib/foo/b"
Current plugin is just about force use aliases instead of relative paths (and back for deprecated aliases).
If you need to sort imports, you may try rule
simple-import-sort/importsfrom https://github.com/lydell/eslint-plugin-simple-import-sort It is very flexible, so you may customize your own groups. For instance, you may group aliases in one group and relative imports to another group. Check their docsSorry, maybe I’m not being clear - I’m not talking about sorting. I’m talking about an ESLint rule that flags alias imports that can be expressed as relative subdirectory imports, but flags other imports that could have been alias imports. Does that make sense?
Examples:
// we're in @/lib/foo // correct import A from "./foobar/a" import B from "./b" import C from "@/lib/c" import D from "@/d" // incorrect import A from "@/lib/foo/foobar/a" import B from "@/lib/foo/b"