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
Describe the bug
Using ESLint with Nuxt config in Nuxt 3 project I am getting violation of import/named rule from import { FontAwesomeIcon } from '@fortawesome/vue-fontawesome'
I am using the latest @fortawesome/vue-fontawesome. The import I copied from the docs and also it works correctly when applied. But the linting error is tedious.
Reproducible test case GitHub repo where I encountered it. It is part of a larger project, but with separate package.json
At the moment, I covered the issue up by a setting inside .eslintrc.json
Describe the bug
Using ESLint with Nuxt config in Nuxt 3 project I am getting violation of import/named rule from
import { FontAwesomeIcon } from '@fortawesome/vue-fontawesome'
I am using the latest
@fortawesome/vue-fontawesome
. The import I copied from the docs and also it works correctly when applied. But the linting error is tedious.Reproducible test case
GitHub repo where I encountered it. It is part of a larger project, but with separate
package.json
At the moment, I covered the issue up by a setting inside
.eslintrc.json
So the import is not checked and the error is not raising.
Expected behavior
Since the import is technically valid, there shouldn't be a clash with ESLint rules.
Desktop (please complete the following information):
Additional context
Opened on request.
The text was updated successfully, but these errors were encountered: