projectPaths cwd and getTsconfig helper (performance issue)

[romanlex]

Anybody who can explain why inside this resolver used getTsconfig function for project config option instead of tsconfig nearest of source file

https://github.com/import-js/eslint-import-resolver-typescript/blob/master/src/index.ts#L366

For example monorepo has meny packages
Settings of import resolver is

Now we get multiple project paths

If I use eslintrc config inside packages with root directive I don't need to know anything about the rest of the tsconfig in the another project.

All this paths participate in calculations every time but all what we need its resolve import path inside only one package.

Why we cant use getTsconfig only for current file?
It would be much faster

[SukkaW]

@romanlex The current implementation is to create multiple path matcher instances with every project provided. This way we can pre-initiate a pool of path matcher instances, otherwise we will have to create a path matcher instance per file. We will then use every path matcher instance against the filesystem individually when resolving a module.

If you have any better ideas about improving this, please don't hesitate to create a PR! I am more than happy to review and merge it!

[JounQin]

See #368, in next major the performance issue will be resolved.

And you can try it out today.

#368 (comment)