Skip to content
This repository has been archived by the owner on Jul 8, 2020. It is now read-only.

gulp protractor - Error: [...] .bin/webdriver-manager ENOENT #490

Open
gruppjo opened this issue Feb 17, 2017 · 3 comments
Open

gulp protractor - Error: [...] .bin/webdriver-manager ENOENT #490

gruppjo opened this issue Feb 17, 2017 · 3 comments

Comments

@gruppjo
Copy link
Contributor

gruppjo commented Feb 17, 2017

The following error occurs due to a problem with gulp-protractor and yarn. Discussion started here: #469

Fix:
In your project folder (be careful with rm!), consider using [trash](https://github.com/sindresorhus/trash).

# remove gulp-protractor and protractor from node modules
rm -rf ./node_modules/gulp-protractor ./node_modules/protractor
# install using npm
npm install

Error:

$ gulp protractor
[13:22:23] Using gulpfile ~/Projects/play/test/gulpfile.js
[13:22:23] Starting 'clean'...
[13:22:23] Starting 'wiredep'...
[13:22:23] Starting 'environment'...
[13:22:23] Starting 'eslint'...
[13:22:24] Starting 'jsonlint'...
[13:22:24] Starting 'webdriver-update'...
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: spawn /Users/jonathan/Projects/play/test/node_modules/.bin/webdriver-manager ENOENT
    at exports._errnoException (util.js:1026:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:359:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
    at Module.runMain (module.js:609:11)
    at run (bootstrap_node.js:382:7)
    at startup (bootstrap_node.js:137:9)
    at bootstrap_node.js:497:3

image

@gruppjo
Copy link
Contributor Author

gruppjo commented Apr 12, 2017

The following updates should take care of this issue:

Gregor

package.json updates fuer yarn + protractor funktionalitaät:

"postinstall": "./node_modules/protractor/bin/webdriver-manager update"

neues devDependency:

"protractor": "^5.1.1",

@gruppjo gruppjo added this to the 1.12.0 milestone Apr 12, 2017
@gruppjo
Copy link
Contributor Author

gruppjo commented Apr 12, 2017

@lordgreg, I still get errors that I don't get with npm when installing and running gulp protractor with yarn:

screen shot 2017-04-12 at 18 04 17

gruppjo added a commit that referenced this issue Apr 12, 2017
* dev: (23 commits)
  update deps
  #490: yarn protractor issues - add protractor and postinstallgs
  #511: component subgenerator - docs
  #511: only generate component with module on main module to avoid component name conflicts
  fix: generators/app/index.js barColor generation for _index.html
  #511: generate component with module
  #511: component-subgenerator - check if module.scss exists with try/catch rather than fs in order to make it work during first run of /generator/app
  #511: component-subgenerator - add import to module's scss
  #511: component-subgenerator - add test file for component, test the subgenerator with other modules than main
  #511: component-subgenerator - finish basic implementation, allow camelCase names
  #511: component-subgenerator - finish basic implementation, with tests and gulpfile update
  #511: component-subgenerator - start implementation
  fix build
  break build
  #495: mattermost - turn slack integration back on
  #481: remove gulp update - fix tests
  #495: mattermost - turn slack integration back on
  #481: remove gulp update
  #512: bower - resolutions for angular 1.5.11
  #481: remove generator apiomat
  ...
@lordgreg
Copy link
Contributor

Hi @gruppjo,

I'm sorry for late response. You will have to wait few days more for me to get back to the personal office space :P

I will clone another demo of generator-m and do the same things I'm always doing.

As soon as I find out what is causing the issue above, I'll post another response.

🎱

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants