@dword-design/eslint-plugin-import-alias

An ESLint plugin that enforces the use of import aliases. Also supports autofixing.

Aliases are a great thing to make imports more readable and you do not have to change import paths that often when a file path is changed.

1import foo from '../../model/sub/foo';
2import bar from '../other/bar';

changes to

1import foo from '@/model/sub/foo';
2import bar from '@/sub/other/bar';

Now what if you are in a bigger team or you have a lot of projects to update. Or you just want to make sure that everything is consistent. This is where a linter comes into the play. This rule allows you to detect inconsistent imports and even autofix them. This works by matching alias paths agains the imports and replacing the import paths with the first matching aliased path.

Install

1# npm
2$ npm install @dword-design/eslint-plugin-import-alias
3
4# Yarn
5$ yarn add @dword-design/eslint-plugin-import-alias

Usage

Add the plugin to your ESLint config:

1import { defineConfig } from 'eslint/config';
2import importAlias from '@dword-design/import-alias';
3
4export default defineConfig([
5  importAlias.configs.recommended,
6]);

Alright, now you have to tell the plugin which aliases to use. In the simplest case, you are already using babel-plugin-module-resolver for your aliases. Your babel config would look something like this:

1{
2  "plugins": {
3    ["module-resolver", {
4      "alias": {
5        "@": ".",
6      },
7    }]
8  }
9}

In this case lucky you, you don't have to do anything else. The plugin should work out of the box.

If you have a special project setup that does not have a babel config in the project path, you can still use the plugin by passing the aliases directly to the rule. In this case you define the rule additionally in the rules section:

1"rules": {
2  "@dword-design/import-alias/prefer-alias": [
3    "error",
4    {
5      "alias": {
6        "@": "./src",
7        "@components": "./src/components"
8      }
9    }
10  ]
11}

By default, the plugin will convert parent paths to aliases (like ../model/foo), but will keep subpath imports relative. You can change that to also convert subpaths to aliased imports by passing the aliasForSubpaths option to the rule like so:

1"rules": {
2  "@dword-design/import-alias/prefer-alias": ["error", { "aliasForSubpaths": true }]
3}

Contribute

Are you missing something or want to contribute? Feel free to file an issue or a pull request! ⚙️

Support

Hey, I am Sebastian Landwehr, a freelance web developer, and I love developing web apps and open source packages. If you want to support me so that I can keep packages up to date and build more helpful tools, you can donate here:

 If you want to send me a one time donation. The coffee is pretty good 😊.
 Also for one time donations if you like PayPal.
 Here you can support me regularly, which is great so I can steadily work on projects.

Thanks a lot for your support! ❤️

License

MIT License © Sebastian Landwehr