un-ts/eslint-import-resolver-ts

This plugin adds TypeScript support to `eslint-plugin-import`.

eslint-import-resolver-ts's Issues

Usage with baseUrl

This resolver is great, it's already solving a number of issues for us.

We're using it with a monorepo and create-react-app, which doesn't support paths - but does support baseUrl set to src. In that case, we can access a folder in ./src/* as an absolute import - i.e. import { Button } from 'components/Button'.

Perhaps I'm missing something, but I'm still getting errors about unresolved imports in this case, and the import/order rule thinks that my import is external, not internal.

Are you able to offer any advice or suggestions here?

What makes this package different from the original one?

This is a fork of alexgorbatchev/eslint-import-resolver-typescript and no where in the README is explained the reasoning for creating and using this instead of the original module.

Would it be possible for you to explain what are the pros and cons of using this versus the original module? I'm just trying to make an informed decision :)

Using globs for `directory` is slow

The recommended config for multiple directories is very slow (./packages/**/tsconfig.json)

This is probably due to the library walking the node_modules directories? Would it be possible to ignore the node_modules folders?

For now, I recommend explicit levels in the directories glob, which is much faster.

"settings": {
    "import/resolver": {
    "ts": {
      "directory": "./*/*/tsconfig.json" // Any package, but don't go deeper than the package root
    }
  }