ng e2e error: Cannot find module 'process-nextick-args'

[WalterLeinert]

Please provide us with the following information:

1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
   Windows 10
2. Versions. Please run ng --version. If there's nothing outputted, please run
   in a Terminal: node --version and paste the result here:
   angular-cli: local (v1.0.0-beta.14, branch: master)
   node: 6.5.0
   os: win32 x64
3. Repro steps. Was this an app that wasn't created using the CLI? What change did you
   do on your code? etc.
   App was created by "ng new foo7", no changes
4. The log given by the failure. Normally this include a stack trace and some
   more information.
   ng e2e

foo7@0.0.0 pree2e d:\Entwicklung\angular2\angular-cli\foo7
webdriver-manager update

module.js:457
throw err;
^

Error: Cannot find module 'process-nextick-args'
at Function.Module._resolveFilename (module.js:455:15)
at Function.Module.load (module.js:403:25)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object. (d:\Entwicklung\angular2\angular-cli\foo7\node_modules\readable-stream\lib_stream
duplex.js:21:23)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\Walter\AppData\Roaming\npm\node_modules
npm\bin\npm-cli.js" "run" "e2e" "--" "./protractor.conf.js"
npm ERR! node v6.5.0
npm ERR! npm v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! foo7@0.0.0 pree2e: webdriver-manager update
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the foo7@0.0.0 pree2e script 'webdriver-manager update'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the foo7 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! webdriver-manager update
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs foo7
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls foo7
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! d:\Entwicklung\angular2\angular-cli\foo7\npm-debug.log

Some end-to-end tests failed, see above.

1. Mention any other details that might be useful.
   After installing process-nextick-args manually (npm install process-nextick-args --save-dev) the e2e tests work.

---

Thanks! We'll be in touch soon.

[seatuna]

I just got this error too. Upgrading node to 6.5 and reinstalling angular-cli fixed it for me!

#1930

[WalterLeinert]

I already used node v6.5.0 and npm v3.10.7 (see above). I'm using the linked version of angular-cli, so I will experiment a little bit.

[WalterLeinert]

I did a fresh reinstall of the linked cli version and cannot reproduce the problem -> closing the issue

[WalterLeinert]

Hi Dmitry,

I closed the issue, because after reinstalling a linked cli I could not reproduce the issue any more.

Regards,

Walter

Von: Dmitry A. Efimenko [mailto:notifications@github.com]
Gesendet: Donnerstag, 15. September 2016 21:13
An: angular/angular-cli angular-cli@noreply.github.com
Cc: WalterLeinert walter.leinert@outlook.com; Author author@noreply.github.com
Betreff: Re: [angular/angular-cli] ng e2e error: Cannot find module 'process-nextick-args' (#2128)

duplicate? #1930 #1930

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #2128 (comment) , or mute the thread https://github.com/notifications/unsubscribe-auth/ALKjZ1HtJo-Q5BAiTpEju_tl9C8ZB_Nlks5qqZjVgaJpZM4J9t8q . https://github.com/notifications/beacon/ALKjZ-Bm3LObZlmoLuLsmsn_f4HVzwM9ks5qqZjVgaJpZM4J9t8q.gif

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}