ESLint v10 support

[ianparkinson]

ESLint v10 is now available - will this plugin be updated to support v10? The package.json file only lists support up to v9.

ESLint v10 drops support for the old .eslintrc configuration file, in favour of the new flat config format. I imagine that will at least involve updating the plugin documentation, and may require dropping support for versions of ESLint prior to v9.

(With thanks for providing this plugin, which has worked very well for me.)

[Limegrass]

Ah, sorry about that! I'll take a look into this within the next week.

[Limegrass]

I pushed an update to declare support for eslint@10; however, it does look like there's some missing support on eslint-plugin-import (eslint-plugin-import#3227) and on neovim's eslint-lsp, so I'm not 100% certain that it works properly.

The CLI appears to work normally, and things appears to display configs properly within eslint's config explorer, but if you're able to verify that v1.6.1 works properly, that would be great.

[ianparkinson]

Hi - thanks for updating this!

I think it's working as expected. My main project has some other upstream dependencies that don't support v10 yet, but I put together a minimal Typescript project and it correctly reported a relative import that could have used the path mapping.

I used the following eslint config:

// @ts-check

import eslint from '@eslint/js';
import { defineConfig } from 'eslint/config';
import tseslint from 'typescript-eslint';
import * as importAlias from "@limegrass/eslint-plugin-import-alias";

export default defineConfig([
  tseslint.configs.strict,
  tseslint.configs.stylistic,
  {
    plugins: { "@limegrass/import-alias": importAlias },
    rules: {
      "@limegrass/import-alias/import-alias": "error",
    },
  },
 ] 
);

...is that the right way to install the plugin using FlatConfig? Your documentation shows something similar for the old .eslintrc format - but the flat config example is rather more complicated.

Thanks again!

[Limegrass]

Thanks for the confirmation. Your configuration there looks valid to me. Both that setup and the one in the examples should work, but I believe your setup would probably have better type support if this package was set-up for it properly. I'll look into that and update the example when I do.