Use `node:` prefix for built-in module imports to support Deno

[watsonarw]

Problem

fdir currently imports Node.js built-in modules without the node: prefix. This prevents fdir from working in Deno, which requires the node: prefix for Node.js compatibility.

Proposed Solution

Update all built-in module imports to use the node: prefix:

• 'fs' → 'node:fs'
• 'path' → 'node:path'
• 'module' → 'node:module'

Benefits

• Deno compatibility: Enables fdir to work in Deno's Node.js compatibility mode
• Explicit imports: Makes it clear these are built-in modules, not user packages
• Security: The node: prefix ensures the node built-in module is used, not something else that's been added to the require cache

Compatibility

The node: prefix has been supported in Node.js since v12.20.0 and v14.13.1.

In fdir package.json, I see support for >=12.0.0, so this might technically be a breaking change. That said, Node 12 was EOL in 2022, and anyone on v12.0 through v.12.19 could update v12.20.

[thecodrr]

Happy to accept a PR!

We can change the minimum Node version to v12.20.0. What do you think @SuperchupuDev?

[SuperchupuDev]

sadly, the node: protocol wasn't available in cjs until node >14 (can't remember exact version). so it wouldn't be possible without dropping node 12 users (also it'd be a breaking change)

[watsonarw]

Ah, I missed the CJS version.

Looks like support for node: imports in CJS was added in v14.18.0

tsdown looks like it's configured to remove it
https://github.com/thecodrr/fdir/blob/master/tsdown.config.ts#L7, but could be changed to use different settings for ESM vs CJS