• @FooBarrington
    link
    16 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)
      • @FooBarrington
        link
        1
        edit-2
        6 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"