NPM js-beautify: different treatment of "-" in command line

[einars]

Is it possible that "-" as a parameter is being treated differently in the situation if the script is run from the git checkout, or from npm install?

js-beautify@1.4.2 installed via npm:
% js-beautify -
Unable to open path "/home/e/-"

git checkout, v1.4.2:
% ./js/bin/js-beautify.js -
[waiting for stdin]

[evocateur]

Yikes. I don't use the - arg very much, maybe there's a dependency version issue? I'll try to look into it later today.

[einars]

I don't use it much either, but there was a confused user in comments for #27 who couldn't find how to use the reading from stdin, and I was surprised that my quick "js-beautify -" verification in the terminal failed.

[kevinoid]

@einars, is it possible that you are using an older version of nopt in your git checkout? It looks like the handling of '-' was changed in npm/nopt@649d969 between nopt v2.1.1 and v2.1.2 where v2.1.1 would return

{
  "argv": {
    "remain": [],
    "cooked": [],
    "original": [
      "-"
    ]
  }
}

while v2.1.2 returns

{
  "argv": {
    "remain": [
      "-"
    ],
    "cooked": [
      "-"
    ],
    "original": [
      "-"
    ]
  }
}

which causes execution to enter the loop at js/lib/cli.js:389.

+1 for supporting js-beautify - again.

[bitwiseman]

We're now up to nopt v3.0.1. 😄
But yes, it is possible to have the npm install'd version use the global node_modules, and the local git version use the local modules, and have them differ.

[cdosborn]

From npm, the command does not seem to handle stdin.

$ js-beautify - <<< "var x = 3"
Unable to open path "my/home/path/blah-"
Run `js-beautify -h` for help.

$ npm -v js-beautify
1.4.3

$ npm version
{ http_parser: '1.0',
  node: '0.10.26',
  v8: '3.14.5.9',
  ares: '1.9.0-DEV',
  uv: '0.10.25',
  zlib: '1.2.3',
  modules: '11',
  openssl: '1.0.1e',
  npm: '1.4.3' }

[bitwiseman]

@cdosborn - Thanks!
Here's a work around for the moment:

$ js-beautify -f - <<< "var x = 3"
var x = 3

There's a pull request already in for improving this area, so maybe this will get into the next release.

[cdosborn]

Thanks, looking forward.

[bitwiseman]

This looks to be fixed for the next version.