Closed danrot closed 7 years ago
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...
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 js-beautify@1.6.14
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 js-beautify@1.6.14
Nice monday, guys :D
+10086
https://github.com/beautify-web/js-beautify/issues/1247#issuecomment-330162127
That's a workaround.
for work now
npm install --save-dev js-beautify@1.6.14
me 2!
npm:
npm install --save-dev js-beautify@1.6.14
yarn:
yarn add js-beautify@1.6.14 --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 js-beautify@1.6.14
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
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:
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.