Pull in shed as an official dependency

[jeffposnick]

It looks like shed is packaged as an npm module, but I don't think it's published. (Unless I'm missing it somewhere.)

We should work with @wibblymat to figure out whether we can start pulling it in via package.json instead of manually copying the source into the project (which was done in #26).

[jeffposnick]

#54 implements a stop-gap approach of pulling in the #master branch via bower.

[jeffposnick]

Hey @wibblymat, what's your timeline for releasing something official?

We're currently [pulling in] "shed": "wibblymat/shed#84fe1e0cd15fd633db9356ce597e58e7483a83da" and I have a feeling you've made some changes in the past few weeks. Anything we should know about/update to?

[wibblymat]

Not sure why I didn't see this issue earlier. I have made a bunch of changes recently, and I think the stuff around upgrade flow is broken in the version you are using.

I'll publish to npm and then create a PR here to use it.

[jeffposnick]

Thanks, @wibblymat! Right now we're using bower to pull in all our client-side JS dependencies, so the gulp build process might have to be tweaked a bit if you're going to use npm.

[wibblymat]

No worries, I published to Bower too.

[jeffposnick]

This was fixed in #499