[no-unresolved]: Unable to resolve path to module with node: protocol specifier

Hi there, thanks for this plugin, super useful! 👍

Ran into an issue when using the new node: prefix for builtin / core modules (currently in v16, but will be backported): import/no-unresolved cannot resolve the path to the module:

import fs from 'node:fs';
                ~~~~~~~
                   ^---- Unable to resolve path to module 'node:fs'  eslint(import/no-unresolved)

[karlhorky]

Ah yeah, in VSCode ESLint extension, it’s still using Node 12:

ESLint server running in node v12.18.3

But on the command line, all is good! 🙌

[karlhorky]

If it’s a monorepo, you may have a central yarn.lock or package-lock.json file that contains the older versions of is-core-module, which you may be able to manually upgrade - for example, upgrading a version in yarn.lock by hand like this: https://www.youtube.com/watch?v=iOYTpHRzL0A