Open bertho-zero opened 2 weeks ago
By default eslint merges the config, making it impossible to use a custom resolver with option without the default resolver node being added.
settings: { 'import/resolver': { [path.resolve(__dirname, './resolver')]: { /* some options */ }, }, },
Then the following resolvers are used:
{ '/home/.../eslint-config/resolver': {}, node: { extensions: [ '.js', '.jsx', '.json' ] } }
settings: { 'import/resolver': { [path.resolve(__dirname, './resolver')]: { /* some options */ }, node: false, }, },
{ '/home/.../eslint-config/resolver': {}, node: false, }
And the node resolver is still used, same with null, undefined or other
I can only disable resolver node by doing this, but I can't pass any options:
settings: { 'import/resolver': path.resolve(__dirname, './resolver'), },
I propose as a solution not to use a resolver if its configuration is equal to false.
By default eslint merges the config, making it impossible to use a custom resolver with option without the default resolver node being added.
Try 1
Then the following resolvers are used:
Try 2:
Then the following resolvers are used:
And the node resolver is still used, same with null, undefined or other
Try 3:
I can only disable resolver node by doing this, but I can't pass any options:
I propose as a solution not to use a resolver if its configuration is equal to false.