-
Notifications
You must be signed in to change notification settings - Fork 16
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
Use pkg
for standalone binary bundling
#511
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Oh this is awesome!!! I don't know exactly what it was that I couldn't use pkg back then but hopefully it works now :) During each
Which internally starts memebox itself soo once the CI goes past the nexe (now pkg) command we'll know if all works out |
Tested it locally awesome!! - it works Thank you for that - that was a long time issue with all the node12 build issues because of nexe - merging that in Would you like to be added to the contributors list? |
My attempt to get
pkg
working as an alternative tonexe
, so we're not bound to Node 12.16.2 anymore. So far seems to work, as far as I could tell, but I didn't test much of any specific features.Probably there is some duplicate in the
package.json
by double-bundlingrelease/*.js
as scripts AND assets. Thought to look into that a bit further, but maybe best to verify that everything works and then we can tweak the settings.You mentioned some special behavior with
nexe
andvm2
for the scripting feature. Maybe you can give that a quick try with this PR or tell me how to test that myself?