Resolver plugins

Is there a way to add a resolver plugin to eslint or I will have to disable the import/no-unresolved rule? Here’s a plugin I use:

const DirectoryNamedWebpackPlugin = require('directory-named-webpack-plugin')

module.exports = {
  resolve: {
    plugins: [
      new DirectoryNamedWebpackPlugin(true)
    ]
  }
}

Tried this but it didn’t work

//.eslintrc.js
module.exports = {
  settings: {
    'import/resolver': {
      plugins: [new DirectoryNamedWebpackPlugin(true)]
    }
  }
}

[egehandulger]

In https://github.com/benmosher/eslint-plugin-import#resolvers I can’t seem to find a way to use a plugin(perhaps I’m missing something)? I also can’t use eslint-import-resolver-webpack because of craco (I tried it without craco but it didn’t catch the plugin as well)

Anyone who comes here in the future. You certainly can use eslint-import-resolver-webpack. In the readme it mentions about this:

Will look for webpack.config.js as a sibling of the first ancestral package.json, or a config parameter may be provided with another filename/path either relative to the package.json, or a complete, absolute path.

Clearly, craco.config.js is not the same as webpack.config.js. To make both modules happy, create a webpack.config.js file as if there is no craco.

const DirectoryNamedWebpackPlugin = require('directory-named-webpack-plugin')

module.exports = {
  resolve: {
    plugins: [new DirectoryNamedWebpackPlugin()],
  },
}

Then, require this file inside craco.config.js and use it where applicable/desired in accordance to craco format.

const webpackCustomConfig = require('./webpack.config')

module.exports = {
  webpack: {
    configure: (webpackConfig) => ({
      ...webpackConfig,
      resolve: {
        ...webpackConfig.resolve,
        plugins: [
          ...webpackCustomConfig.resolve.plugins,
          ...webpackConfig.resolve.plugins,
        ],
      },
    }),
  },
}

For eslint, you can configure webpack as documented in the readme:

settings: {
    'import/resolver': 'webpack',
  },

[shermendev]

A webpack plugin certainly can’t be dropped in to resolver settings;

I see, thank you for clarifying that out.