• @[email protected]
      link
      fedilink
      12 months ago

      It is, but I’d specifically like a rule that enforces this style of import over aliased imports. I.e. when importing a package, the order of importance is:

      1. Relative import (if on same or lower level)
      2. Aliased import (if in ancestor directory or different module)
      • @vitonskyOP
        link
        12 months ago

        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

        • @[email protected]
          link
          fedilink
          1
          edit-2
          2 months ago

          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
          
          // 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"