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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
This repository has a ton of the exact same issues listed #1073
Comments
I was unable to get it working with node 18 or 20. I ended up finding a fork of the pkg project which supports the latest node release. |
I was having the same issue as described above and found out that nexe does include the code in the executable but still looks for the files in the working directory. I'm working in node 18.19.0, nexe installed via npm nexe@4.0.0-rc.4 @calebboyd Since you added the "more inforation needed" tag, I'll add some examples: Single fileindex.js (D:\src)
results in test.exe If we run test.exe in D:\src, we get the following: However if we move the test.exe to a different folder (in this case D:\test) and run test.exe, we get the following:
But if we add an empty index.js file next to the test.exe, we once again have our Multiple filesImage we have multiple files:
D:/src/controllers/controller.js
In my larger project where I'm using typescript, then run nexe in the dist folder containing the regular js files, I have also found that the modules I've created and import using require("./foo/bar"), are usually not included in the project. But if I specifically include them using npm packages
ConclusionThe code is included (even though you might have to include them using the |
Is anyone still managing this repo?
#1050, #1030, #1028, #954 etc are all the same issue, nexe's core purpose
馃帀 create a single executable out of your node.js apps
fails to do so.Is this broken or what? -r "./node_modules/**/*" does nothing to help, just bloats the file size.
The text was updated successfully, but these errors were encountered: