ENOENT error for spawning child processes about args

[ntwcklng]

Okay, defaults to use the .js extension would break a lot of projects.
Whats wrong with npm link and adding the binaries to package.json? Then you can also test your bins with node ./bin/gest-test.js

[mfix22]

Actually, I am with you there. Thanks for challenging my point, I agree!

[mfix22]

Here is an example of what I was thinking:

// Generate full name of binary
const bin = module.parent.exports.bin
const full = this.binary + '-' + (Array.isArray(details.usage) ? details.usage[0] : details.usage)
const binFull = path.join(__dirname, bin[full] || `${full}.js`)
...
this.child = spawn(binFull, args, {

[ntwcklng]

I also experimented with this a while ago - my working example was:

const bin = process.mainModule.filename
const subCommand = (Array.isArray(details.usage) ? details.usage[0] : details.usage)
const fullPath = path.join(bin.split(path.sep).slice(0, -1).join(path.sep) + '/' + this.binary + '-' + subCommand)
const ext = path.extname(bin)
let binFull = fullPath

if (ext.length > 0) {
  const withExt = path.basename(bin, ext) + '-' + subCommand + ext
  binFull = path.join(bin.split(path.sep).slice(0, -1).join(path.sep) + '/' + withExt)
}

this.child = spawn(binFull, args, {
...

The problem with that is that you have to chmod +x all binaries while developing. Otherwise you get Error: spawn EACCES.
I think adding the binaries to the package.json and run npm link is the easiest and best solution. See #46

[mfix22]

@ntwcklng I have not had a problem with that since I test my 'binaries' as node ./bin/gest-test.js [options], so I don't run into the EACCES error. I think the solution I posted tackles two issues: 1. it defaults to looking in package.json for the paths to your binaries and 2. defaults to use a .js extension if you don't put them in package.json.

The only two issues I was running into was that the it wasn't finding the file without __dirname and secondly it was looking for a binary without the .js extension (which I would like to keep for syntax highlighting etc.)

[ntwcklng]

We should document this process better

[mfix22]

@ntwcklng yeah it was really just a matter of my understanding how args worked. If anything, documenting better should be a different issue. Closing.