Tony Ross

Thanks @ivanagui2! One more thing: I don't see `hint` or `@hint/*` packages listed in the `npm ls` output. Did you remove `hint` from your project? If so that's fine, but...

Glad to hear you got it sorted out. Since you used a temporary cache, you may still need to run `npm cache clean --force` to keep the issue from returning...

Closing since this has been identified as a local issue with the `npm` cache.

@Melvin-Abraham does this mean you ran into this particular issue as well? If so I'm starting to think `the npm cache self-heals from corruption issues` isn't as accurate as that...

@Melvin-Abraham > Maybe that is true but what if instead of clearing the cache, the packages are installed forcefully without relying on cache with something like --no-cache flag. I'd definitely...

@Melvin-Abraham reactivating this issue given our discussion here. Would you be interesting in taking a stab at this? The relevant install code lives here https://github.com/webhintio/hint/blob/main/packages/extension-vscode/src/utils/webhint-packages.ts

Thanks for letting us know @Jefftopia! Just to confirm, when you look at VS Code's "Output" window for webhint, are you seeing the following message in the log? Or something...

I like the idea of not maintaining a granular list here since we don't need to vary behavior on specific audio/font/image/video types. Seems if there are any exceptions it'd be...

@dependabot rebase

Note: TS is still outputing a `require` call for the `async import` so this appears to be also blocked until the new module support for `nodenext` ships in TS.