Juan Navarro

Hi @hartrene , nice catch! I've been asking around, and the issue seems to come from an update in the Docker base image. The owners of this code are currently...

I tend to avoid writing paths by hand to avoid this kind of mistakes; in this case I ran a `find` command (`find . | grep libvosk.so`) and copied the...

You're right! Good catch, I hadn't even realized it. Now, following this clue... note that Vosk loads the library as mentioned in my previous comment: ```js path.join(__dirname, "lib", "linux-x86_64", "libvosk.so")...

I'll look more deeply into this. I'm not doing anything strange at all; my work dir has been written as `/home/code/myapp/` in my examples, to simplify, but in reality is...

Testing with the repro case, the full prefix (/home/...) is not included in any of the paths that start with /snapshot/, so including this in my original report seems either...

Note: I've edited the repro code, so the "assets" array contains paths to concrete files, instead of catch-all wildcards. I.e. before: ```js "assets": [ "node_modules/ffi-napi/**/*", "node_modules/ref-napi/**/*", "node_modules/vosk/lib/**/*" ], ``` after:...

EDIT -- I was mentioning *node-gyp-build* but it really doesn't seem to have anything to do with the issue. OK so the problem seems to be that *pkg* patches Node's...

@robertsLando thanks a lot for the tips and guidance given so far! One issue I'm finding is that the "dlopen" that *pkg* has, is a wrapper for Node's `process.dlopen`, which...

It does work! :-D I was 100% focused on using the existing functionality of *pkg*, but of course you are right, by duplicating a bit the code found in *prelude/bootstrap.js*,...

I'm not sure of what is the actionable conclusion of this issue. While I found a solution, we might argue that it is just a workaround and that maybe *pkg*...