paulirish/speedline

npm ERR! enoent ENOENT: no such file or directory, chmod ../speedline/cli.js

hinok opened this issue · 5 comments

hinok commented

Hey,
While installing speedline as global package

npm i -g speedline

I get errors:

npm ERR! Darwin 15.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "speedline"
npm ERR! node v5.11.0
npm ERR! npm  v3.9.6
npm ERR! path /Users/hinok/.node/lib/node_modules/speedline/cli.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/hinok/.node/lib/node_modules/speedline/cli.js'
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/hinok/.node/lib/node_modules/speedline/cli.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/hinok/npm-debug.log

My env

OS X 10.11.5
Node 5.11.0
npm 3.9.6

I also use prefix in .npmrc to install all modules in my home directory

prefix=/Users/hinok/.node

I've found also that this one works but It doesn't put binary in PATH to execute (quite obvious).

npm i --no-bin-links -g speedline

Is it problem on my side or is it something wrong with package?

This problem doesn't occur when I install older version 0.1.3

npm install -g speedline@0.1.3
/Users/hinok/.node/bin/speedline -> /Users/hinok/.node/lib/node_modules/speedline/cli.js
/Users/hinok/.node/lib
└─┬ speedline@0.1.3
  ├─┬ babar@0.0.3
  │ └── colors@0.6.2
  ├─┬ devtools-timeline-model@1.1.4
  │ ├── chrome-devtools-frontend@1.0.382117
  │ └── resolve@1.1.7
  ├── jpeg-js@0.1.2
  ├─┬ loud-rejection@1.5.0
  │ ├─┬ currently-unhandled@0.4.1
  │ │ └── array-find-index@1.0.1
  │ └── signal-exit@3.0.0
  └─┬ meow@3.7.0
    ├─┬ camelcase-keys@2.1.0
    │ └── camelcase@2.1.1
    ├── decamelize@1.2.0
    ├── map-obj@1.0.1
    ├── minimist@1.2.0
    ├─┬ normalize-package-data@2.3.5
    │ ├── hosted-git-info@2.1.5
    │ ├─┬ is-builtin-module@1.0.0
    │ │ └── builtin-modules@1.1.1
    │ ├── semver@5.1.0
    │ └─┬ validate-npm-package-license@3.0.1
    │   ├─┬ spdx-correct@1.0.2
    │   │ └── spdx-license-ids@1.2.1
    │   └─┬ spdx-expression-parse@1.0.2
    │     └── spdx-exceptions@1.0.4
    ├── object-assign@4.1.0
    ├─┬ read-pkg-up@1.0.1
    │ ├─┬ find-up@1.1.2
    │ │ ├── path-exists@2.1.0
    │ │ └─┬ pinkie-promise@2.0.1
    │ │   └── pinkie@2.0.4
    │ └─┬ read-pkg@1.1.0
    │   ├─┬ load-json-file@1.1.0
    │   │ ├── graceful-fs@4.1.4
    │   │ ├─┬ parse-json@2.2.0
    │   │ │ └─┬ error-ex@1.3.0
    │   │ │   └── is-arrayish@0.2.1
    │   │ ├── pify@2.3.0
    │   │ └─┬ strip-bom@2.0.0
    │   │   └── is-utf8@0.2.1
    │   └── path-type@1.1.0
    ├─┬ redent@1.0.0
    │ ├─┬ indent-string@2.1.0
    │ │ └─┬ repeating@2.0.1
    │ │   └─┬ is-finite@1.0.1
    │ │     └── number-is-nan@1.0.0
    │ └─┬ strip-indent@1.0.1
    │   └── get-stdin@4.0.1
    └── trim-newlines@1.0.0

Hi, I have the exact same problem but on Windows with Node 6.

Windows 7
Node v6.2.1
NPM v3.9.3

Here's the log dump:

verbose stack Error: ENOENT: no such file or directory, chmod 'C:\Users\myuser\AppData\Roaming\npm\node_modules\speedline\cli.js'
verbose stack     at Error (native)
verbose cwd C:\Dev
error Windows_NT 6.1.7601
error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "speedline"
error node v6.2.1
error npm  v3.9.3
error path C:\Users\myuser\AppData\Roaming\npm\node_modules\speedline\cli.js
error code ENOENT
error errno -4058
error syscall chmod
error enoent ENOENT: no such file or directory, chmod 'C:\Users\myuser\AppData\Roaming\npm\node_modules\speedline\cli.js'
error enoent ENOENT: no such file or directory, chmod 'C:\Users\myuser\AppData\Roaming\npm\node_modules\speedline\cli.js'
error enoent This is most likely not a problem with npm itself
error enoent and is related to npm not being able to find a file.
verbose exit [ -4058, true ]

Thanks for the reports -- this will require a bit of investigation

It seams that, I removed the cli.js file from the build.
@hinok @koriolis It should have been fixed in 0.2.1.

hinok commented

@pmdartus Solved! ;)

Perfect let me close that.