passing args provider on the command line about nexe HOT 5 CLOSED

Found was the issue - the commandline tool used directly process.argv[2] , normally it was called with

node stats.js config.js => having the config.js as arg2

after compile it is

./statsd config.js => having the config.js as arg1

from nexe.

Should be a simple fix - probably just need to unshift node to process.argv[0]. I'll add this over the weekend.

from nexe.

I still have to pass a first arg to the built binary to get it working (on 0.2.8)...

Works:

./app whatever --taget test --ttl 10

Does not work:

./app --taget test --ttl 10

In the second case the params seems to be passed to node itself? I'm not sure...

from nexe.

This seems like incorrect behavior to me (and makes adding native module support harder than it needs to be as it messes with binding libraries that would be useful).

The first argument needs to be the executable. node, is no longer the executable the built app is (yes i know that is actually node, but you know what I mean) so that should be the first argument.

Rather than shifting node into the first argument we should splice "nexejs" into the second argument, leaving the built executable as the first argument and all actual args to follow after.

In this way argv to the module will indeed look right ([0] = executable, [1] the node root module, [2] argument, ect ...)

from nexe.

Have you tried enabling the flags option on compile time?

from nexe.