Adding browser-sync to the kit.

[tsmorgan]

This addresses issue #84.

I've changed the findAvailablePort function in utils.js to include a callback which passes back the port number.

Then in server.js I start the the app either with or without browser-sync depending on whether we're in production or not.

[joelanman]

is it possible to avoid the callback in server - just put the function in utils?

[joelanman]

I had a go at moving all the code into lib/utils.js:

https://github.com/alphagov/govuk_prototype_kit/tree/browser-sync-joelanman

[tsmorgan]

Sorry @joelanman I was out yesterday. That looks fine to me. I was only really concerned about not risking breaking the findAvailablePort function or making it more opaque to others by adding more and more logic inside it. I like your solution though.

[joelanman]

do you think we need ghostMode? It's kind of fun, but doesn't it mean you can't view the prototype on two browsers/devices independently? Won't they always be synced with the page their looking at/scroll position etc?

[joelanman]

Thinking open: true could be useful, so the prototype opens in the browser automatically

[joelanman]

closing in favour of #193