Getting error on Node.js >=v22.13.0 but not on <=v22.12.0

[TobiWo]

Hi there,

I'm getting the following error on Node.js >= v22.13.0:

> Error! Cannot read file, ENOENT
  node:sqlite
> Error! ENOENT: no such file or directory, open 'node:sqlite'

I do not use sqlite nor any of my dependencies. I'm not sure whether this is pkg related or Node.js related. Any help is much appreciated.

[robertsLando]

@TobiWo Are you getting this isseu while compiling?

[faulpeltz]

Node 22.13 unflagged sqlite (it was behind an experimental flag before)
Which Node version are you running pkg with?

[robertsLando]

He is using latest node 22.13 binaries

[faulpeltz]

Sorry no idea without digging through the code, maybe pkg doesn't know about the "node:" prefix for internal package names?

[robertsLando]

Maybe our resolve (https://www.npmjs.com/package/resolve) doens't works with node:, I should check

[robertsLando]

Could be worth a try bumping it to latest, didn't notice they did a release few months ago

[robertsLando]

@TobiWo try with 6.3.2

[TobiWo]

I randomly tested with nodejs v21.7.0 and it works as well.
I checked release notes. sqlite was bumped from 22.12.0 to 22.13.0 fixing floating point issue. But this does not have anything to do with my issue. This means nothing changed in terms that sqlite is available in all nodejs version.

I actually see the require statement in the respective undici library but no idea what to do with that information. I also updated undici to the latest version. Still the same issue.

I coonducted a deepsearch with Grok and these are his findings:

3. Module Resolution and Packaging Tool Behavior:
In v22.12.0, the debug log "Cannot find module 'node:sqlite'" suggests the packaging tool attempted to resolve 'node:sqlite' but proceeded without it, possibly due to a fallback or ignoring the module.
In v22.13.0, the logs indicate the tool is trying to add 'node:sqlite' to a queue for bytecode, stat info, and content, then fails with "ENOENT: no such file or directory, open 'node:sqlite'".
This suggests the tool is treating 'node:sqlite' as a file path, attempting to open it directly, which fails because 'node:sqlite' is a module name, not a file.

4. Potential Causes:
Misinterpretation of Built-in Modules: The packaging tool likely uses a mechanism to resolve module paths, such as 'require.resolve'. For built-in modules, 'require.resolve' returns the module name (e.g., 'node:sqlite'), not a file path. In v22.13.0, the tool may be trying to open this name as a file, leading to the error.
Change in 'undici' Behavior: 'undici', used for fetch requests, has a cache feature that may use 'node:sqlite' ([Undici Documentation](https://undici.nodejs.org/)). If 'undici' requires 'node:sqlite' more strictly in v22.13.0, it could trigger the packaging tool to attempt inclusion, exacerbating the issue.
No Apparent Changes in Node.js Module Resolution: Reviewing the Node.js change logs for v22.13.0, there are no explicit changes to how built-in modules are loaded or resolved, suggesting the issue lies in the packaging tool's handling.

[TobiWo]

Hi @faulpeltz @robertsLando, do you have any update on this 😬 ? I quickly tested with 6.4.0 and nodejs 22.14.0. Still the same error 😢 .

[robertsLando]

Sorry unfortunately nope

[robertsLando]

Maybe we have a fix #152

[TobiWo]

Hi @robertsLando , sorry for the delay. I just checked it and I can confirm that this PR fixed the packaging issue. Thank you 🙏 .

[robertsLando]

Perfect, thanks for the feedback