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

browsersync instead of livereload #228

Closed
gruppjo opened this issue Aug 10, 2015 · 2 comments
Closed

browsersync instead of livereload #228

gruppjo opened this issue Aug 10, 2015 · 2 comments

Comments

@gruppjo
Copy link
Contributor

gruppjo commented Aug 10, 2015

Browsersync may be better in a couple of cases for us:

  • automatically uses a free livereload and browser port (livereload requires hard-coded values)
    • thus: several watch tasks (of different projects) could run at the same time
    • also: gulp watch could be run alongside other tasks that use gulp serve (e.g. gulp protractor etc...)
    • also: gulp protractor could be terminated by calling browserSync.exit()
    • one-click weinre
  • it prints the url with the port for the user
@gruppjo
Copy link
Contributor Author

gruppjo commented Sep 3, 2015

Some more tweaks will be necessary to get all of the above features to run.

@gruppjo gruppjo modified the milestones: 1.3.0, 1.4.0 Sep 3, 2015
@MathiasTim
Copy link
Contributor

I'm not sure, but shouldn't it be possible with browsersync, that you can run multiple projects with out getting: EADDRINUSE ?

I tried it with the demo repo and got this:
screen shot 2015-09-05 at 13 23 14

With protractor everything is fine (operates on different ports I assume?!).
But, don't get me wrong. Browsersync is great. Just the one click weinre is so cool :)

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