Last version of js-beautify breaks vue-cli installation

[LucaBlackDragon]

Steps to reproduce:

Run npm i -g vue-cli in terminal

Expected behavior:

vue-cli should install

Actual behavior:

The installation fails and this error is logged:

error path C:\Users\<my-user-folder>\AppData\Roaming\npm\node_modules\vue-cli\node_modules\js-beautify\js\bin\css-beautify.js
error code ENOENT
error errno -4058
error syscall chmod
error enoent ENOENT: no such file or directory, chmod 'C:\Users\<my-user-folder>\AppData\Roaming\npm\node_modules\vue-cli\node_modules\js-beautify\js\bin\css-beautify.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.

Notes:

An issue has already been opened in js-beautify repo:
beautifier/js-beautify#1247

[jddxf]

For a quick fix, you can install yarn and run yarn global add vue-cli.

[LinusBorg]

Seems this has to be solved in js-beautify. Good to know that yarn seems to work, though I wonder why.

[jddxf]

@LinusBorg https://github.com/vuejs/vue-cli/blob/master/yarn.lock#L3192.
If we have a package-lock.json in this repo, npm would also work.

Edit: npm-shrinkwrap.json instead of package-lock.json here would make npm work.

[chanlito]

@jddxf thanks, yarn works.

[LucaBlackDragon]

@jddxf I think an npm-shrinkwrap.json would be even better in this case: command line tools (such as vue-cli) are among the recommended use-cases mentioned in npm official documentation:

The recommended use-case for npm-shrinkwrap.json is applications deployed through the publishing process on the registry: for example, daemons and command-line tools intended as global installs or devDependencies.

[jddxf]

@LucaBlackDragon You're right. I didn't realize the difference between package-lock.json and npm-shrinkwrap.json.

One key detail about package-lock.json is that it cannot be published, and it will be ignored if found in any place other than the toplevel package.

So having a package-lock.json would not make npm work here.

[LinusBorg]

@LucaBlackDragon That's a good point, we should think about using that.

/cc @vuejs/collaborators do you have any thoughts on this one?

[lianghx-319]

yarn not install with npm but with the msi in win10 can install the cli successfully

[HerringtonDarkholme]

Vue-cli doesn't depend on js-beautify directly. But some dependency bumped its dependency on js-beautify and that breaks us.

I would give a thumb up for npm-shirnkwrap.json, which is designed for avoiding such scenario.

The recommended use-case for npm-shrinkwrap.json is applications deployed through the publishing process on the registry: for example, daemons and command-line tools intended as global installs or devDependencies.

https://docs.npmjs.com/files/shrinkwrap.json

[egoist]

@HerringtonDarkholme hmm lockfile actually wouldn't work for end users, I think you mean npm-shrinkwrap.json

[HerringtonDarkholme]

@egoist Sure. Thanks for correction.

[sanderkoenders]

Pull request is up, just needs permission to merge: beautifier/js-beautify#1251

[posva]

dup of #591