# eslint-import-resolver-jest
_"I like my `testutils` where I can see 'em"_ 🕵🏽♀️
If you're using [jest](https://facebook.github.io/jest/) and you have installed custom name mappings in your config via the `moduleNameMapper` config and you're using the wonderful [eslint-plugin-import](https://github.com/benmosher/eslint-plugin-import) you might get yelled at by eslint:
(I oftentimes create an alias for the helpers I use for testing)
### Let's fix this!
```shell
yarn add eslint-import-resolver-jest -D
```
or
```shell
npm i eslint-import-resolver-jest -D
```
If you are using the [`package.json`](https://facebook.github.io/jest/docs/configuration.html) config option from jest everything should _just work_™.
If you are using a separate config file for jest using the `--config` option you have to point this plugin to it, too (in your .eslintrc):
```json
"settings": {
"import/resolver": {
"jest": {
"jestConfigFile": "./jest.conf.json"
}
}
}
```
That's it!
If you want to ensure that this resolver only applies to your test files, you can use ESLint's `overrides` configuration option:
```json
"overrides": [
{
"files": ["**/__tests__/**/*.js"],
"settings": {
"import/resolver": {
"jest": {
"jestConfigFile": "./jest.conf.json"
}
}
}
}
]
```
#### Note
It will only resolve the modules in your test files that you specified via `testRegex` or `testMatch` in your jest config.
### Contributing
Create issues in this repo or get active yourself:
```shell
yarn test # npm test works, too
```
### License
MIT
