Node built-in modules aren't detected when prefixed with node:

[shroudedcode]

Expected Behavior

Since v16 (and in previous versions through backporting) Node.js supports an alternative way to import built-in modules (like fs) which involves prefixing the module's name with node:. Using this syntax, importing fs looks like this:

import fs from 'node:fs'

This is functionally equivalent to the following:

import fs from 'fs'

Hence, it should also link to the same thing: the Node.js documentation page for that module.

What actually happened?

Currently, Octolinker generates a link with the href attribute set to node:process, which results in Chrome trying to open the "URL" process with an application assigned to the node scheme/protocol. That doesn't seem right.

URL

https://github.com/sindresorhus/globby/blob/43eccf41a800a5dedb3b3fcdf313f7daf5c199ff/index.js#L1

Anything else we should know?

No response

[shroudedcode]

Thanks @xt0rted and @stefanbuck, love the extension! 🙌