We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
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.
The text was updated successfully, but these errors were encountered: