You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2025. It is now read-only.
To set a thought. There is eslint-import-resolver-typescript. I have tried to use it. Here is wrong error messages in different packages.
The only solution here would be that libraries adapt to it or that you bring your own patches. The first would be an okay solution, but it takes time. Or the developers do not want to adapt their own library especially for this plugin. The second solution would be rather unattractive.
Therefore I decided against eslint-import-resolver-typescript because in all it does not offer enough added value.
eslint-plugin-import
The problems here should actually be fixed by eslint-import-resolver-typescript. This is of course not an option if further errors are caused by it. You end up with an infinite rat tail here.
Currently I make it easy for myself and the solution is to disable eslint for one line:: // eslint-disable-next-line import/no-unresolved
eslint-import-resolver-typescript
To set a thought. There is eslint-import-resolver-typescript. I have tried to use it. Here is wrong error messages in different packages.
The only solution here would be that libraries adapt to it or that you bring your own patches. The first would be an okay solution, but it takes time. Or the developers do not want to adapt their own library especially for this plugin. The second solution would be rather unattractive.
Therefore I decided against eslint-import-resolver-typescript because in all it does not offer enough added value.
eslint-plugin-import
The problems here should actually be fixed by eslint-import-resolver-typescript. This is of course not an option if further errors are caused by it. You end up with an infinite rat tail here.
Currently I make it easy for myself and the solution is to disable eslint for one line::
// eslint-disable-next-line import/no-unresolved
I will observe the whole thing and decide in the future whether I will change something.
Here are a few more links:
import-js/eslint-plugin-import#2132
import-js/eslint-import-resolver-typescript#186
import-js/eslint-import-resolver-typescript#31
The text was updated successfully, but these errors were encountered: