Runtime issue with loadable extensions when using ncc for single-file builds

[tn233]

I ran into a runtime problem when using ncc to compile a single file for executable applications (Node.js): Loadable extension for ... not found. Was the ... package installed?

I dug into it and found out what caused the issue in index.cjs (lines 41–46):

const loadablePath = join(
    __dirname,
    "..", // this was the problem for me
    packageName,
    `${ENTRYPOINT_BASE_NAME}.${extensionSuffix(platform)}`
  );

To fix it, I copied the extension directory to the parent directory of the working directory, and it worked.

It might be helpful to add an optional argument like options.nativeBinding in better-sqlite3, or maybe automatically look for files in the current working directory. But I’m not sure if that would make the project more complicated. (By the way, I couldn’t even find the repository for this javascript glue code.)