You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This package is unable to resolve native dependencies when they exist in a parent node_modules folder.
Currently, I have to make a copy of them using something like find-up in a postinstall script to properly run my executable in my consumer app.
The text was updated successfully, but these errors were encountered:
Yeah, In order to use additional binaries you'll need to ship them alongside your app/nexe binary.
You can use a project like the vercel/ncc bundler (and indirectly https://github.com/vercel/webpack-asset-relocator-loader) To make a more concise set of files that are bundled, and subsequently written out at runtime for the bundled app to link to.
Thanks for the response.
That makes total sense, though I was really hoping to avoid a bundler. 😆
I saw a few issues in the nexe repo related to this.
You might want to put an example in the readme in that to use additional binaries section to help guide folks to a proper solution.
This package is unable to resolve native dependencies when they exist in a parent
node_modules
folder.Currently, I have to make a copy of them using something like
find-up
in apostinstall
script to properly run my executable in my consumer app.The text was updated successfully, but these errors were encountered: