eslint.config.js

[cristofermartins]

I only got it to work in eslint flat config files like this:

import { defineConfig } from "eslint/config";
import globals from "globals";
import js from "@eslint/js";
import pluginImport from "eslint-plugin-import";

export default defineConfig([
  { files: ["**/*.{js,mjs,cjs}"] },
  { files: ["**/*.{js,mjs,cjs}"], languageOptions: { globals: {...globals.browser, ...globals.node} } },
  { files: ["**/*.{js,mjs,cjs}"], plugins: { js, pluginImport }, extends: ["js/recommended"] },

	{
		rules: {
      // modules
      "pluginImport/no-mutable-exports": "error",
      "pluginImport/named": "error",
    },
	},
]);

It is working. The linting gives me an error when i try to export a let or a var.

i'm not using the pluginImport inside the extends array since i want to turn on each rule by my self.

Also when i use extends: ["js/recommended", pluginImport.flatConfigs.recommended] i'm able to use the import name inside the rules config, but the named rule starts to give me a problem:

1:30 error Unable to resolve path to module 'eslint/config' import/no-unresolved

I'm new to javascript and linting.
Thanks in advance.

[ljharb]

That's an issue with eslint, not this plugin.

[cristofermartins]

@ljharb Hey, thanks for the answer. Do you know how i can fix this?

[ljharb]

Ah, on a reread it seems like an issue with this plugin.

Specifically, we use resolve, which doesn't support exports yet. So, the best workaround in the meantime is an eslint override comment.

[JounQin]

Duplicate of #1810

Try https://github.com/import-js/eslint-import-resolver-typescript