Unable to resolve path to module .." (import/no-unresolved) about linters-config

[OlukaDenis]

Well, It has worked. Thank you!

[MauricioRobayo]

Hi @OlukaDenis, thanks for raising this issue.

It is OK to disable some rules when there is no way around it, but please don't do it on your .esling.config.js, just add a disable comment next to the line you want to disable and with the specific rule you want to disable: https://eslint.org/docs/user-guide/configuring#disabling-rules-with-inline-comments

So, in your case, you can add the following comment above the offending line:

// eslint-disable-next-line no-unresolved
import '@fortawesome/fontawesome-free/js...';

Doing it this way makes it clear you are making a valid choice there because there is no way around, and you don't have to modify the ESLint configuration provided. If you disable it on the whole file with a comment, or in the ESLint configuration, then it won't be clear why you are disabling it and if it is a valid choice to do it.

You can use this same method for other cases when there is no way around.

Please let us know if this works for you.

[MauricioRobayo]

Sorry, I close it by accident 😄 .