Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Native Modules go unresolved #13

Open
please-rewrite opened this issue Jan 27, 2022 · 2 comments
Open

Native Modules go unresolved #13

please-rewrite opened this issue Jan 27, 2022 · 2 comments

Comments

@please-rewrite
Copy link

please-rewrite commented Jan 27, 2022

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.

@calebboyd
Copy link
Member

Hey @please-rewrite

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.

@please-rewrite
Copy link
Author

please-rewrite commented Jan 27, 2022

Hey @calebboyd!

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.

I'd be happy to add it myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants