gulp-protractor | gulp wrapper for protractor tests | Frontend Framework library

It could simply be because your app needs a lot of memory to be built; node.js has a hard 1.4Gb limit for memory allocations. See this question on how to increase this limit. Let us know if this helps!

Ok, I have the solution to this problem,

1. command "jspm unbundle" this command clean every build of the project.

2. and command "jspm install aurelia-history-browser" update the browser.

This usually means that one of the other project dependencies in your project.json has a dependency of lodash and they have not patched their pacakge.json.

The error states which one it is: "browser-sync-spa" and the path to it:

In your devDependencies, try downgrading this:

The problem was that toastr is using the following command, that is expecting a module to be installed.

I used gulp with gulp-angular-protractor like below, hope this helps. It will work for gulp-protractor plugin as well.

//Gulpfile

It seems that your node-gyp requires java to be built correctly. The thing with Heroku's architecture is that it only provides you what you specify/need. Right now I don't think Heroku understands that it needs a JVM to run your application. So you should provide a buildpack. A build pack put very simply is a set of rules telling Heroku what to set-up, install and build. There is a buildpack for JVM called heroku/jvm. So, what you have to do is add this to your application through the dashboard or your CLI via heroku buildpacks:add heroku/jvm.

There is one more thing to do. Since your app requires javac at build time itself, we should pull up the build order for java/jvm . So in that case you should probably do heroku buildpacks:add --index 1 heroku/jvm. This puts the JVM buildpack at position 1 and pushes every other buildpack down the order.

Now when the app starts building, it first sets up the JVM (thus enabling javac for your instance) and then runs the NodeJS build. This build will now pick up the javac from the current instance and build accordingly.

Ref: Mulitple Buildpacks in Heroku

I found it, according to the e2e testing site of AngularJS: https://docs.angularjs.org/guide/e2e-testing everything is divided into code blocks. So within describe function you have beforeEach, afterEach and it. And I put my 'it' functions within 'beforeEach'.

Here is my best guess at what's going on:

1. You are launching with the selenium standalone server locally using your ip address and a port that is not 4444. This means that you did not select seleniumAddress: "http://localhost:4444/wd/hub" or directConnect: true. I'll have a code snippet below of what this looks like.

2. If you are launching locally and not on Travis, then Protractor launches by the Chrome browser by default. This also means that you should have downloaded the ChromeDriver.

3. You should upgrade from Protractor 2.5 to the latest. Protractor is strongly coupled with the entire stack: selenium-webdriver, the standalone server, browser drivers and browsers. If you are using an up-to-date browser and Protractor 2.5, then probably webdriver-manager downloaded old binaries that may be incompatible with your browser.

Here is the code snippet: