Develop Reference

How do I fix permission denied error after upgrading dependencies?

I am facing the following issue. Any help is highly appreciated.
I am upgrading one dependency in my project as per White-source advice: normalize-url, from the version 4.5.0 to 4.5.1 in order to fix security vulnerabilities.
The application runs fine and I have to test a search call which gets a 200 code and shows a response of a JSON found in "/initial-db.json".
But, After I just run npm install normalize-url#latest I can see the version in the package-lock.json is getting upgraded, but when I test my application, the search call gets a 500 code with the following error:
Error: EACCES: permission denied, open '/prod/msp/apps/src/data/initial-db.json'
at Object.openSync (fs.js:476:3)
at writeFileSync (fs.js:1467:35)
at FileSync.write (/prod/msp/apps/node_modules/lowdb/adapters/FileSync.js:53:14)
at LodashWrapper.db.write (/prod/msp/apps/node_modules/lowdb/lib/main.js:37:21)
at /prod/msp/apps/node_modules/json-server/lib/server/router/write.js:5:8
at Layer.handle [as handle_request] (/prod/msp/apps/node_modules/express/lib/router/layer.js:95:5)
at next (/prod/msp/apps/node_modules/express/lib/router/route.js:137:13)
at create (/prod/msp/apps/node_modules/json-server/lib/server/router/singular.js:37:5)
at Layer.handle [as handle_request] (/prod/msp/apps/node_modules/express/lib/router/layer.js:95:5)
at next (/prod/msp/apps/node_modules/express/lib/router/route.js:137:13)
I also tried to run npm update normalize-url --depth 7 as I saw in some suggested answers and I get the same behaviour.
I also ran npm ls normalize-url and then I updated the all the dependencies in the tree, but still with the same results.
Any idea could help. :)

meteor fails to start server in events.js with write EOF exception

When I try to start a meteor project I always get this error message (on my machine only, the project is working fine on my colleague's machines):
=> Started proxy.
=> Started MongoDB.
events.js:141
throw er; // Unhandled 'error' event
^
Error: write EOF
at exports._errnoException (util.js:907:11)
at WriteWrap.afterWrite (net.js:785:14)
Sometimes the error already shows up before mongo is stared.
In fact, I cannot start any project anymore ... :-(
It seems that I have a serious problem with my meteor installation.
I tried re-installing meteor, but no effect.
meteor reset --> no effect
Could it be a problem with a downloaded package? Where does meteor store the packages?
I really would appreaiate any hint what I can try to make it work again.
I'm using meteor on windows.

selenium webdriver manager update - npm

I tried to update the selenium webdriver using the "webdriver-manager", but i get the error as,
Error: Got error Error: read ECONNRESET from https://selenium-release.storage.googleapis.com/2.48/selenium-server-standalone-2.48.2.jar
Error: Got error Error: read ECONNRESET from https://selenium-release.storage.googleapis.com/2.48/selenium-server-standalone-2.48.2.jar
fs.js:60
throw err; // Forgot a callback but don't know where? Use NODE_DEBUG=fs
^
Error: EPERM: operation not permitted, unlink 'C:\Users\user_name\AppData\Roaming\npm\node_modules\protractor\selenium\selenium-server-standalone-2.48.2.jar'
at Error (native)
I am not sure what was the cause. I tried updating the protractor too, but no luck.
Also i tried running the command prompt as administrator and run
webdriver-manager update --ignore_ssl
Please help.

I have solved the issue as below,
// Update chrome alone
webdriver-manager update --standalone=0 --chrome --alternate_cdn http://chromedriver.storage.googleapis.com/
// Update selenium alone
webdriver-manager update --chrome=0 --standalone --alternate_cdn http://selenium-release.storage.googleapis.com/

I was facing same issue and got the below error when running update chrome driver.
Error: Got error Error: self signed certificate in certificate chain from https://chromedriver.storage.googleapis.com/2.21/chromedriver_win32.zip
I manually downloaded the driver saved it as node_modules\protractor\selenium\chromedriver_2.21.exe
and it worked. I was running it from my office network

it actually works over http as well: http://selenium-release.storage.googleapis.com/2.48/selenium-server-standalone-2.48.2.jar , just find-replace it inside the library.
Or download it manually to: node_modules/protractor/selenium

i had same problem.
Solution for me was updating node.js (best way to do it - just download latest version and install it).

Apache cordova ,Unable to create an app

This is the output , knowing that i'm running it under a proxy , and i specified the proxy settings.
npm config set proxy http://proxy.company.com:8080
npm config set https-proxy http://proxy.company.com:8080
then i run this command to create a new app in the specified folder "hello".
C:\>cordova create hello com.example.hello HelloWorld
Creating a new cordova project with name "HelloWorld" and id "com.example.hello"
at location "C:\hello"
Downloading cordova library for www...
this is the error :
Error: connect ETIMEDOUT
at errnoException (net.js:904:11)
at Object.afterConnect [as oncomplete] (net.js:895:19)

I recently had the same issue. I was maintaining an existing app and updating Cordova was well beyond the scope of the current task, so getting this working was really my only option.
Firstly, in order to eliminate all the errors and warnings about deprecated APIs when installing Cordova, I had to use some really ancient package managers. Using NVM I installed node 0.10.48 and npm 1.4.29. Cordova 3.6.3 then installed without any complaints.
But even creating an empty Cordova project wasn't possible as the below output shows:
Creating a new cordova project with name "HelloWorld" and id "com.example.hello" at location "~/Downloads"
Downloading cordova library for www...
Error: HTTP error 404 retrieving version 3.6.3 of cordova for www
at Request._callback (~/.nvm/v0.10.48/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/lazy_load.js:230:30)
at Request.self.callback (~/.nvm/v0.10.48/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/request/index.js:148:22)
at Request.emit (events.js:98:17)
at Request.<anonymous> (~/.nvm/v0.10.48/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/request/index.js:886:14)
at Request.emit (events.js:117:20)
at IncomingMessage.<anonymous> (~/.nvm/v0.10.48/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/request/index.js:837:12)
at IncomingMessage.emit (events.js:117:20)
at _stream_readable.js:944:16
at process._tickCallback (node.js:458:13)
Adding some extra debug output to lazy_load.js revealed that the CLI was looking for a directory at ~/.cordova/lib/www/cordova/3.6.3.
Since this was a brand new installation of Cordova, that directory obviously wasn't present so it went to download an archive from https://git-wip-us.apache.org/repos/asf?p=cordova-app-hello-world.git;a=snapshot;h=3.6.3;sf=tgz but the archive that used to be there has apparently been removed. I found it at https://github.com/apache/cordova-app-hello-world/releases/tag/3.6.3.
I download that archive and extracted it to ~/.cordova/lib/www/cordova/3.6.3, and I was then able to create my template app.
I know this thread is old but I really hope this helps someone. Working with Cordova is a bitch at the best of times, let alone when vital online components are removed like this.

On OSX Yosemite even with sudo the error persists.

after digging a little bit more. i found the solution.
I have just run the cmd.exe as administrator. after that worked like magic.

I ran into this problem by not installing cordova as admin. I had to sudo npm install -g cordova to get the create command to work.

Meteor on windows - Server crashes on code push

I installed Meteor for windows from here :
http://win.meteor.com
The server crashes almost every time I try to make live code push.
I would then have to end the mongod.exe process and run 'meteor reset' and 'meteor' to start it up back again.
Here are the logs:
=> Meteor server restarted
events.js:71
throw arguments[1]; // Unhandled 'error' event
^
Error: This socket is closed.
at Socket._write (net.js:519:19)
at Socket.write (net.js:511:15)
at Socket.HttpProxy.proxyWebSocketRequest.reverseProxy.incoming.socket.on.listeners.onOutgoing (C:\Program Files\Meteor\lib\node_modules\http-proxy\lib\node-http-proxy\http-proxy.js:515:35)
at Socket.EventEmitter.emit (events.js:96:17)
at TCP.onread (net.js:397:14)
Anyone on the same boat? I read from here https://github.com/meteor/meteor/issues/513 that this has been an open issue for over 6 months.
Someone's got any workaround? Help appreciated.

The EADDRINUSE issue was fixed in 0.6.3.1-rev4, but please update to version 0.6.4 as this problem seems to have resolved the other issue by the update to the http-proxy package.
For MSI downloads see https://github.com/sdarnell/meteor/wiki/Windows
Should also appear on http://win.meteor.com soon

This is a known issue with windows for meteor : https://github.com/sdarnell/meteor/issues/7. The one on meteor's github repo might also be related. I have it too! Hopefully they sort it out soon!. Just ctrl+c to stop your server before you edit code and get it back up after you're done.
Even if you start it after this sometimes you could also get an ADDRINUSE error, which is quite frustrating.