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
If eslint.config.js contains an await keyword, config-inspector will throw an error.
Extra context:
In my config case of the following image:
Removed the await at L13 allows config-inspector to shows all the configs normally (withNuxt() returns a Promise), ESLint ran from CLI also seems to works, but the VSCode IDE's ESLint server will not be able to infer the configs of withNuxt() and will complain about things like no-undef because globals from withNuxt() isn't registered.
The text was updated successfully, but these errors were encountered:
Unfortunately, top-level await is not yet supported because of unjs/jiti#72, where it is still required to properly bail out module cache for re-imports. You might need to workaround to not use top-level await at this moment.
If
eslint.config.js
contains an await keyword,config-inspector
will throw an error.Extra context:
In my config case of the following image:
Removed the
await
at L13 allowsconfig-inspector
to shows all the configs normally (withNuxt()
returns a Promise), ESLint ran from CLI also seems to works, but the VSCode IDE's ESLint server will not be able to infer the configs ofwithNuxt()
and will complain about things likeno-undef
because globals fromwithNuxt()
isn't registered.The text was updated successfully, but these errors were encountered: