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
Anybody who can explain why inside this resolver used getTsconfig function for project config option instead of tsconfig nearest of source file
getTsconfig
project
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.
root
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
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Anybody who can explain why inside this resolver used
getTsconfig
function forproject
config option instead of tsconfig nearest of source filehttps://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
The text was updated successfully, but these errors were encountered: