dword-design / eslint-plugin-import-alias Goto Github PK

Hi,

I don't get how to use the prefer-alias rule. There is no example in the documentation.

I'm using it this way atm but it doesn't work :

"@dword-design/import-alias/prefer-alias": {
        "@components": "./src/components",
        "@api": "./src/api",
        "@assets": "./src/assets",
        "@constants": "./src/constants",
        "@context": "./src/context",
        "@hook": "./src/hook",
        "@icons": "./src/icons",
        "@screens": "./src/screens",
        "@styles": "./src/styles",
        "@types": "./src/types",
        "@utils": "./src/utils"
      }

Thanks

Hi - I'm having trouble with getting this plugin working. I followed the instructions in the README and get this error:

Error: Failed to load config "plugin:import-alias/recommended" to extend from.

👋

When importing from the same directory, this rule doesn't get applied. It considers this valid:

import { Foo } from './foo'

Expectation:

import { Foo } from '@/path/to/foo'

All my valid imports have the error: Unexpected subpath import via alias

Real world example:

Unexpected subpath import via alias '@lib/constants/a2.constants'. Use './constants/a2.constants' instead

Configuration in .eslintrc.js:

'@dword-design/import-alias/prefer-alias': [
  'error',
  {
    'alias': {
      '@lib': './src/'
    }
  }
],

Is there a way to get this to work with . and not just ..?

I'm using Nuxt, and Nuxt maps the "root" directory to ~~. Because of this mapping, VSCode will often autocomplete paths to, say, a script file, to something like:

import { Foo } from '~~/legacy/scripts/Foo'

However, to reduce verbosity in commonly-used paths, I have aliases like ~js to refer to ~~/legacy/scripts.

What I would like is the ability to rewrite not just relative paths to alias paths, but alias paths to other alias paths.

So, on save (or eslint --fix), I would like the above re-written to:

import { Foo } from '~js/Foo'

Is it possible to include more customization into what is re-written? This seems somewhat related to #133, in that some customization / filters would be nice.