Js-beautify: Installing js-beautify fails

Created on 18 Sep 2017  ·  249Comments  ·  Source: beautify-web/js-beautify

Description

I am trying to install a library, which is dependant on this one, and starting today (I've tried the last week the last time) I get the following error when installing my dependencies:

npm ERR! path /Users/daniel.rotter/Development/massiveart/sulu-minimal/vendor/sulu/sulu/node_modules/js-beautify/js/bin/css-beautify.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/daniel.rotter/Development/massiveart/sulu-minimal/vendor/sulu/sulu/node_modules/js-beautify/js/bin/css-beautify.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/daniel.rotter/.npm/_logs/2017-09-18T05_55_47_583Z-debug.log

It looks to me like this is somehow connected to the latest 1.7.0 release... Any ideas?

Steps to Reproduce

Create a new folder and install this library as dependency using npm install js-beautify.

Environment

OS: Mac OSX 10.11.6

Deleted most of the PR template, since it's not relevant.

Most helpful comment

@IvanFan I am sure other libraries haven't updated to this version yet. So just add the following line to your dependencies:

{
    "dependencies": {
        "js-beautify": "1.6.14"
    }
}

Mind the missing ^.

All 249 comments

me 2 we are preparing the latest update and now we fucked...

@IvanFan fucked is a little bit exaggerating IMO... Just use npm install [email protected] for now, that will work until a fix is released.

We are using some third-party npm packages which are using js-beautify...
Any idea how to force other dependencies to use the old version?

@IvanFan I am sure other libraries haven't updated to this version yet. So just add the following line to your dependencies:

{
    "dependencies": {
        "js-beautify": "1.6.14"
    }
}

Mind the missing ^.

we are fucked...

we are fucked...

we are fucked...

[email protected] breaks the project installation and trying to use the lower version 1.6.14 for solving this issue

Just found this. vue-cli is breaking as a result.

we are fucked

I think some npm packages are using "js-beautify": "^1.6.14" at the moment...

@IvanFan webpack

@IvanFan Doesn't matter, if your project defines it without ^ it will install exactly this version. ^1.6.14 means >= 1.6.14 && < 2.0, so it "works" with every of these versions.

{
    "dependencies": {
        "js-beautify": "1.6.14"
    }
}

Adding this into the dependencies solved the build in our CI, should be good for a temporary fix. Thanks @danrot

@danrot how do I fix webpack ?

works thx @danrot :)

@zuolin777 You don't have to, just add "js-beautify": "1.6.14" into your package.json dependencies, then it should work.

we are fucked!!!!
i can't work now.

@benjamin658 thx, it works

This bug report is only just over 30 minutes old for an upload that is only 1 hour old. How about giving the poor developer a chance to fix it? Or even better, providing a pull request to fix it?

Be my guest to make a PR. This is just a notification to the dev to show what the impact is of this issue.

vue-cli fails to install

vue-cli npm install works well if you add dependency in package.json
"js-beautify": "1.6.14",

@brianmay Finally somebody reasonable... It's not like we all have to stop working now, the temporary fix is quite easy.

My guess would also be that this library is primarily maintained in the spare time of the contributors, and I don't think that the attitude in this issue is very motivating... So I'd like to say thank you for the great work, and in advance for fixing this issue 😃

The problem is that I can't install vue-cli itself..

I can't install vue-cli itself 2

npm install [email protected] success.

npm install [email protected] failed.

Temporary fix https://npm.r2net.pro/#/detail/js-beautify or you can checkout tag v1.6.14 then host it locally.

But what to do with other packages that depend on this pack?

@oronoa Add this package in your package.json with version lock for 1.6.14. It will override others.

@danrot Thanks!

Temporary fix for vue-cli:

Do not install it globally but in a temp folder.

mkdir C:\vue_cli_temp
cd C:\vue_cli_temp
npm install [email protected]
npm install vue-cli

Then you can use the vue-cli installed like this:

C:\vue_cli_temp\node_modules\.bin\vue init simple MyVueProject

me too, this save me

npm install -g [email protected]

+1

edit: npm install --save [email protected] worked

Thanks for suggestion to add "js-beautify": "1.6.14" to dependencies, saved my bacon while working with vuejs

Pushing code on a Sunday evening and going to sleep. Safe to say, Monday will be interesting to say the least.

@ArmandJ77 Which template are you using? I tried and retried and couldn't get it to work. Tried different node versions as well.

People, just add "js-beautify": "1.6.14" under dependencies in your package.json.
I had a problem with the vue pwa template but this solves it.
Don't panic ;-)

I guess yarn doesn't like this workaround.

@eric-naguras
thank you eric

+1

Yarn would not even report an error, NPM did. So I'm dropping Yarn, back to NPM

I install vue-cli use cnpm。it tell me “ no such file or directory, chmod 'C:UserszxrnhAppDataRoamingnpmnode_modulesvue-clinode_modules_js-beautify@[email protected]

this is my code
cnpm install -g vue-cli
who can help you !

@sobrown See my comment above.

+1

😓

:sob:

+1

Noooooooooooooooooooooooooooooooo

+1

+1

Same here, we found out in a production release (thanks to npm cache).

+11

Stop the fucking "+1" without any information.

+2

Confirmed :)

fuck me

I was getting ready to jump off a cliff before stumbling here. :joy_cat:

+1

+1

Can we please stop posting "+1". It's useless, doesn't help the developer, and spam this issue with non-constructive comments. We're developers, we hate useless bug tickets with no information, let's NOT do the same things to fellow developers.

this is the issue (ty @gafung ) :)

@briced We all know that one guy...
21743186_1094977500632127_3965491206705224243_n

ahn7 s qg41o eo lf tdsv

try yarn 👍

try yarn

yarn install

doesn't fix anything for me, probably because I didn't have a yarn.lock file previously

we are fucked

but yarn solved my problem

A stack trace from my webpack config

Module build failed: Error: Cannot find module './lib/beautify'
        at Function.Module._resolveFilename (module.js:470:15)
        at Function.Module._load (module.js:418:25)
        at Module.require (module.js:498:17)
        at require (internal/module.js:20:19)
        at /efs/clientasg12q/lsae/node_modules/js-beautify/js/index.js:74:27
        at Object.<anonymous> (/efs/clientasg12q/lsae/node_modules/js-beautify/js/index.js:80:7)
        at Module._compile (module.js:571:32)
        at Object.Module._extensions..js (module.js:580:10)
        at Module.load (module.js:488:32)
        at tryModuleLoad (module.js:447:12)
        at Function.Module._load (module.js:439:3)
        at Module.require (module.js:498:17)
        at require (internal/module.js:20:19)
        at Object.<anonymous> (/efs/clientasg12q/lsae/node_modules/vue-loader/lib/template-compiler.js:4:16)
        at Module._compile (module.js:571:32)
        at Object.Module._extensions..js (module.js:580:10)
        at Module.load (module.js:488:32)
        at tryModuleLoad (module.js:447:12)
        at Function.Module._load (module.js:439:3)
        at Module.require (module.js:498:17)
        at require (internal/module.js:20:19)
        at loadLoader (/efs/clientasg12q/lsae/node_modules/loader-runner/lib/loadLoader.js:13:17)
        at iteratePitchingLoaders (/efs/clientasg12q/lsae/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
        at runLoaders (/efs/clientasg12q/lsae/node_modules/loader-runner/lib/LoaderRunner.js:362:2)
        at NormalModule.doBuild (/efs/clientasg12q/lsae/node_modules/webpack/lib/NormalModule.js:182:3)
        at NormalModule.build (/efs/clientasg12q/lsae/node_modules/webpack/lib/NormalModule.js:275:15)
        at Compilation.buildModule (/efs/clientasg12q/lsae/node_modules/webpack/lib/Compilation.js:149:10)
        at factoryCallback (/efs/clientasg12q/lsae/node_modules/webpack/lib/Compilation.js:337:12)
        at factory (/efs/clientasg12q/lsae/node_modules/webpack/lib/NormalModuleFactory.js:241:5)
        at applyPluginsAsyncWaterfall (/efs/clientasg12q/lsae/node_modules/webpack/lib/NormalModuleFactory.js:94:13)

@abdullah Do you have a yarn.lock file in your project? If you do, yarn use this file to get the locked versions of your dependencies, so you don't download the last (broken) version.

me too, same problem

@abdullah Do you have a yarn.lock file in your project? If you do, yarn use this file to get the locked versions of your dependencies, so you don't download the last (broken) version.

guess I'll be switching to yarn for good after this mess is fixed.

In a laravel-mix and vue environment (maybe other setups too) easy fix can be:

npm install --save-dev [email protected]

Building now works for me.

npm 5 (bundled with node 8) generate a package-lock.json and do the same version-locking system.

npm 5 (bundled with node 8) generate a package-lock.json and do the same version-locking system.

Alright, cool.

+1

npm ERR! Linux 4.4.0-93-generic
npm ERR! argv "/.nvm/versions/node/v6.11.3/bin/node" "/.nvm/versions/node/v6.11.3/bin/npm" "i"
npm ERR! node v6.11.3
npm ERR! npm  v3.10.10
npm ERR! path /js-beautify/js/bin/css-beautify.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/js-beautify/js/bin/css-beautify.js'
npm ERR! enoent ENOENT: no such file or directory, chmod '/node_modules/js-beautify/js/bin/css-beautify.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 

Can fix this problem now!!

npm install [email protected]

Nice monday, guys :D

+10086

for work now
npm install --save-dev [email protected]

me 2!

npm:
npm install --save-dev [email protected]
yarn:
yarn add [email protected] --dev

Add this to your package.json file:

  "resolutions": {
    "js-beautify": "1.6.14"
  }

+2

+3

  "bin": {
    "css-beautify": "./js/bin/css-beautify.js",
    "html-beautify": "./js/bin/html-beautify.js",
    "js-beautify": "./js/bin/js-beautify.js"
  },

These three JS files not exist in 1.7.0 released pkg.

https://github.com/beautify-web/js-beautify/issues/1247#issuecomment-330165554

These three JS files not exist in 1.7.0 released pkg.

Now we're getting somewhere. :thinking:

Someone please delete every instance of +1 and those rude comments in this thread. People seem to have no manners anymore ...

@LinusBorg, I kinda enjoy the show :popcorn:

If you have problem with running your vue-cli project npm install [email protected] fixed the problem for me.

Im fuck today of this

Same here, but then how do I start the npm run dev it gives the log of:

> cross-env NODE_ENV=development webpack-dev-server --open --inline --hot

sh: cross-env: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! vue-cli@ dev: `cross-env NODE_ENV=development webpack-dev-server --open --inline --hot`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the vue-cli@ dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/gsm/.npm/_logs/2017-09-18T09_18_56_345Z-debug.log

npm install -g vue-cli --registry=https://registry.npm.taobao.org
can resolve for now

+1

+1

+1

Guys.. "plus ones" are so annoying and useless.

Again, just use the previous tag until this gets fixed.

vue-loader is fucked. I wasted 40 minutes thinking something was wrong with my webpack config.

What is a work around to start a vue-cli dev server, with npm run dev?

We are fucked

i'm trying this issue https://github.com/beautify-web/js-beautify/issues/1247#issuecomment-330171050 i will tell you if it works @tst11

+1

All right @floriandorre ! :)

I solved the problem this way:
1)rm -rf node_modules/
2)npm install --save-dev [email protected]
3) add in package.json:
"resolutions": {
"js-beautify": "1.6.14"
}
4)npm i

@tst11 this isn't working for me XD

悲伤逆流成河

also I had a problem with node-sass today:
I solved the problem this way:
1)npm update
2)npm install
3)nodejs node_modules/node-sass/scripts/install.js
4)npm rebuild node-sass
maybe someone will come in handy

Can not fix it use below steps

  • Remove yarn.lock and node_modules
  • Add old version(@1.6.14) to dependencies
  • yarn

The steps is incorrent? @danrot

haha 论lock 的重要性

+3
We are also facing the same issue

the only issue i found is to use a pre-build repo :/

sequelize-cli also breaks. Just waiting for the fix that I hope gets done today.

vue-loader breaks in 1.7

shits happens

强帖留名!

https://github.com/floriandorre/pre-build-vue-cli
for those who rly need vue-cli today (npm install is already done you can npm run dev)

Workaround: create a shrinkwrap for your project and force dependency versions for affected packages (e.g. vue-loader for me).

Create a npm-shrinkwrap.json file alongside where your package.json lives, add the following:

{ 
  "dependencies": { 
    "vue-loader": { 
      "version": "^13.0.1", 
      "dependencies": { 
        "js-beautify": { 
          "version": "1.6.14" 
        } 
      } 
    } 
  } 
}

You may need to adjust version numbers, and if you have multiple dependencies relying on js-beautify you'll have to list them all in there.

Please either un-publish the current version, or fix it ASAP...!

I can't install vue-cli, because this error crashes, omg :C

this works for me.

package.json:

  "resolutions": {
     "js-beautify": "1.6.14"
   }

@steven-qi Where is the package.json file stored? Trying to install vue-cli but I can't.

@gbaggaley I don't use vue, so I cannot answer your question. For node.js/npm based project, it is right in the root folder of project/package.

Change my package.json to version 1.6.14 helps to me for the "sequelize-cli" issue:
...
"dependencies": {
...
"request": "^2.81.0",
"js-beautify": "1.6.14",
"sequelize": "^4.8.2",
...

We can't install vue-cli, change dev dependency is not working.

try to downgrade vue-cli package to some previous version also

It makes no sense, because webpack just pulls out the latest version of this module.

This worked for us:-

Create npm-shrinkwrap.json parallel to package.json

{ 
  "dependencies": 
   { 
     "js-beautify": 
     { 
        "version": "1.6.14"
      }
    } 
} 

This will work even if js-beautify is internally used in some other packages.

I apologize, but can you give a way where to create this file? I used linux, but I installed windows, and I do not know where to put this file.

I know people are frustrated by this, myself included.

However, hotfixing it through ones package.json-file isn't going to look neat in the long run, if you have multiple developers on a project. Suddenly you're installing older versions of packages you don't really need, but are needed by some other dependency.

I'm sure an issue with, at the moment, 157 comments will get the attention of the developers. And I'm sure it'll all be fixed very soon, as I see several PR's have already been made.

@hydrostasis just create a file npm-shrinkwrap.json parallel to package.json. Create this file manually as you create others.

No, i want install vue-cli, but i can't, there is no file packedge.json.

Can this bug fix it quickly? I have a project to go online tonight

@hydrostasis (or anyone else using vue-cli), see https://github.com/beautify-web/js-beautify/issues/1247#issuecomment-330171050.

@adam-lynch ty :3

@hydrostasis
npm install -g vue-cli --registry=https://registry.npm.taobao.org
try this

+1

+1

+1

Ran into this issue as well...

sad. vue-cli and vue-loader breaking cuz of this.

@steven-qi comments solved my issue with vue-loader.

add this to package.json.

"resolutions": {
     "js-beautify": "1.6.14"
   }

you broke vue :'(

@amit27kmr worked for me. thx

@amit27kmr worked for me. thanks.

@MSMcBain this sollution worked!

I've tried both adding "resolutions" to package.json and the npm-shrinkwrap.json solution, neither work. Build server is still getting this error on TeamCity:

[npm install] npm ERR! enoent ENOENT: no such file or directory, chmod '<path on build server>\node_modules\js-beautify\js\bin\css-beautify.js'

Guys, you broke the Internet... :(

@kallebornemark you should try this: @amit27kmr

{ 
  "dependencies": 
   { 
     "js-beautify": "1.6.14"
    } 
} 

We are fucking!

Same same – older version as suggested works.

I try the add the "js-beautify": "1.6.14" in the not only "dependencies" also "devDependencies" , but they don't work!

This worked for me

npm install -g npm

Then

npm install [email protected]

Broken here as well

As stated here multiple times - use the older version of js-beautify
npm install [email protected]

Stop with the +1 so people can easily see the solution while the poor dev tries to fix things

This worked for me

rm -rf node_modules/
npm install [email protected]
npm install
npm install cross-env
npm run dev

Just the day I started with vue-cli xD

What caused this problem? It still doesn't work for me with webpack builds. Am fucked.

sequelize-cli broken as a result of this issue

can't believe this issue has cost me 3 hours of my life :rage:

This worked yea,

rm -rf node_modules/
npm install [email protected]
npm install
npm install cross-env
npm run dev

Me too. still doesn't work.

Tried one of the above, solutions by locking the version

+1
Not working for me too.

+1
Not working for me too.

昨晚上开始的

me too in Japan

+1
nuxt can not install ! fucked me a day!

Stop fucking this issue!!!)
Let's create a PR, devs!

@vivian-xu Tried it, getting the same error.

we are fucked...

@YevheniiHerasymchuk there is one, https://github.com/beautify-web/js-beautify/pull/1251

everyone stop

Does someone have a working solution (to install vue-cli) ?

If you are facing issues because of a global dependency like me, make sure to install as follows:

RUN npm set progress=false && \
    npm install -g [email protected] [email protected] [email protected] [email protected]

Having multiple RUN statements won't so install everything in one.

@floriandorre
npm install -g vue-cli --registry=https://registry.npm.taobao.org
I resolve by this

@huysh3 i tried and have the same issue

I'm trying all the above hacks but nothing worked so far. I try to deploy my app with now and the webpack build fails:

Module build failed: Error: Cannot find module './lib/beautify'

I added the resolution to package.json without success. Any other idea what to add?

This issue is breaking the laravel npm install as well...

As a temporary workaround I've manually replaced files in vue-loadernode_modulesjs-beautify with 1.6.14 version

nothing works 🙄

Hi Guys,

So theres files missing in the actual package.
Just add these files into the js folder
Archive.zip

I got nothing

we sovled it by change the vertion at yarn.lock and install angain, and it worked! out of fucking,🤔

hopelesss, fucked by the issue.

the issue i have is that i can't install vue-cli not just js-beautify....
i can get js-beautify with your solution but i still not have vue-cli

+1 :-1:

clear cache and reinstall 1.6.14

It looks like somebody got a good story to tell when will be a grandpa: _"That day when I screwed up the whole programming world"_

You broke whole thing :1st_place_medal:

js-horrorify.

use yarn instead...

Go to https://yarnpkg.com/lang/en/docs/install/
Install Yarn
Execute _yarn global add vue-cli_

which doesn't help with laravel... :D

When will this problem be resolved? :(

When they find someone who has the permission to merge PR's... https://github.com/beautify-web/js-beautify/pull/1251

@bitwiseman @evocateur @einars
Annotating three top contributors if that helps

This issue made my day

This is the most monday of any monday I have had for a long time.

Me too @littlephild

fuck it im switching everything to perl

What a shit monday ha?

Step one. Convince boss we should use vue.
Step two. This issue.
edit: Ok, we should probably not use this as a chat.. Sorry.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! Linux 4.9.41-moby
npm ERR! argv "/usr/local/nvm/versions/node/v6.9.1/bin/node" "/usr/local/nvm/versions/node/v6.9.1/bin/npm" "install"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! path /usr/src/app/node_modules/js-beautify/js/bin/css-beautify.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/src/app/node_modules/js-beautify/js/bin/css-beautify.js'
npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/src/app/node_modules/js-beautify/js/bin/css-beautify.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!     /usr/src/app/npm-debug.log

the day, they drove my source-code down... singz in country

To install vue-cli: npm install -g [email protected] vue-cli

Install vue-cli with yarn then
just replace js-beautify section in yarn.lock of your application with this:
js-beautify@^1.6.3: version "1.6.14" resolved "https://registry.yarnpkg.com/js-beautify/-/js-beautify-1.6.14.tgz#d3b8f7322d02b9277d58bd238264c327e58044cd" dependencies: config-chain "~1.1.5" editorconfig "^0.13.2" mkdirp "~0.5.0" nopt "~3.0.1"

this worked for me. I copied it from an older vue project.

@niahmiah Thank you! Your solution works for me!

@niahmiah Thank you! Your solution works for me!

Same here, installing our package now crashes because of this. We had to release patch for last 3 versions replacing "js-beautify": "^1.6.4", with "js-beautify": "~1.6.4",

In Mac ,use the methods before ,It's OK for me,but the windows is wrong.

not working for sequelize-cli

@niahmiah solution works, ty soo much i can finally work ! ('npm install -g [email protected] vue-cli')

@ ustbhuangyi thanks teacher

we are fucked.

I assume it's an honest mistake, but come on, these things should be well tested before rolled out...

rm -rf node_modules/
rm -rf yarn.lock
add this to package.json

"resolutions": {
     "js-beautify": "1.6.14"
 }

yarn
ok

Temporarily, if you have a local copy of your project which work, try npm-shrinkwrap, update all the reference to js-beautify and add the npm-shrinkwrap.json file.

You will fix all version of all dependencies of your project but with with a working version of js-beautify if you npm. As soon as the latest version will be fixed, remove the npm-shrinkwrap.json file.

for vue-cli
vue-init webpack project-name
cd project-name
npm install [email protected] --save-dev
npm install
works for me

adding "js-beautify": "1.6.14", to my package.json worked. Thanks @weizs

npm is npm - shame, it would quite easy to avoid such situations, just make dummy package.json with most used packages and before someone updates any of those, make sure this dummy thing builds.

+1

fucked!

Facing the same issue for the past couple of hours !

+1!

Wish I could lock this thread, this is fucking ridiculous.

WE ARE AWARE OF THE ISSUE, STOP SPAMMING AND USE THE POSTED WORKAROUNDS.

Just go back and use react / angular already.

@evocateur People is having important issues because of this, at least let them express it, otherwise we won't know how big the impact is.

Adding

,
  "resolutions": {
    "js-beautify":"1.6.14"
  }

to the end of your package.json and running yarn also works

@amatiasq they can just upvote the issue, no reason to write what already has been said while making it harder to find workarounds.

I wonder if this will be as historically remembered as when leftpad was deleted from npm.

@evocateur possibility to slam others maybe will make this global npm problem solved one day. Everyone hates npm now.

Global installation of "js-beautify" to solve the problem
cnpm install [email protected] -g

@evocateur that's helpful for people but it's also a huge issue as Atom/Atom-Beta packages are broken and there is not a good way to force those internal packages. The atom package manager (apm) and the packages for Atom Editor are broken since many of them including atom-beautify use this package directly.

I agree that if you are on NPM/Yarn project you can easily and quickly fix this but for other users, this is quite breaking.

Oh look, what's this? :open_mouth:

A link to the official /beautify-web/js-beautify gitter so you don't have to spam here?

Truly revolutionary!

@weizs Are you using yarn install --flat ?

"resolutions": {
"js-beautify": "1.6.14"
}

I have the same problem.

Windows 10.

everybody panic

@muro25 Your solution worked for me!

@RuinSain, Windows 10 is a real serious problem. Get rid of it immediately!

Emergency fix for vue-loader is incoming: https://github.com/vuejs/vue-loader/commit/97bd432bba4350988bfd0db6d7a1a514b66a9826

@CubixSystem yarn need 1.x.x

me 2 and i fixed it with
"dependencies": {
"js-beautify": "1.6.14",
....
}

Btw...post mortem... "Don't publish unnessessary files" ;)

https://github.com/beautify-web/js-beautify/pull/1241

I don't have permissions to the repo anymore, but I still have ownership of the npm package. I just published v1.7.1 that contains all necessary files.

Please, stop spamming this thread. As soon as @bitwiseman is back on the grid, he can handle the PR and whatnot.

Important update for everyone that used these fixes in vuejs

Time to remove "js-beautify": "1.6.14" from your "dependencies":{} and "resolve":{}
[email protected] has been published, please update.

https://twitter.com/vuejs/status/909785891941617664

@niahmiah @Sun1ive thanks。 It's very useful to me.

Hey @bitwiseman could I suggest locking this thread just so save yourself the spam. Appreciate all the work you do.

@evocateur, what's the difference between v1.7.1 and v1.7.2?

@qm3ster You can compare versions on GH yourself, you know ;)

https://github.com/beautify-web/js-beautify/compare/v1.7.1...v1.7.2

@TheLarkInn Thanks for the suggestion. 😄

To everyone else,

_I apologize_.

The issue is fixed.

I thought I had sufficient test coverage and I did not. Tests will be implemented to protect against this before the next release (#1254).

Also, this break highlights the need to create a beta channel for releases and a way to request feedback on beta releases (#1255).

Finally, the project has been maintained by mostly one person over the past year or so, with some additions by other individuals. This break also highlights the need for this project to have a few more people who have the ability address issues/emergencies (#1256).

Help with these would be appreciated.

PS: I thought I'd delete a bunch of the "+1" and "me too" comments until I realized there were over 200 of them. 😱

Was this page helpful?
0 / 5 - 0 ratings

Related issues

aeschli picture aeschli  ·  4Comments

keeganstreet picture keeganstreet  ·  6Comments

retan picture retan  ·  3Comments

iofjuupasli picture iofjuupasli  ·  4Comments

smonff picture smonff  ·  6Comments