Alec Wenzowski

Yarn `1.3.2` currently parses and resolves `jquery@x.*` to `3.2.1` but it would be nice to make `jquery` optional. For more see #17

I [would imagine](https://github.com/josephg/node-browserchannel/pull/55) the example chatserver was written assuming connect 1.7.2. Browserchannel is [currently tested](https://github.com/josephg/node-browserchannel/commit/61eb4200be497b43b4573428685b1dcaf6f5efa8) against express 4.

Figured this would stay in the backlog for a bit. Marked #23 as ready. If you add the other features as issues as well, I'll keep an eye on [the...

Thanks @Dashed I've been meaning to check out babel for some time. This might be a good excuse to try out some es6

lol @3rd-Eden assuming the expectation is that es6 eventually won't require compilation, but that is [a ways off](http://kangax.github.io/compat-table/es6/)

Good to know. PR updated. This now 1. denies access to server-only files 2. sets `Cache-Control:public, max-age=0` on css 3. sets `Cache-Control:public, max-age=31536000` on all other static files By setting...

This is setting http headers for the client and all intermediary caches to interpret. Let me know if a better walkthrough is necessary

I thought something like that might be in the works. Thanks for the instructions. If I get to that change before you ditch the stylesheet I'll send a PR.

The reason this PR exists is to add `Cache-Control:public, max-age=31536000` headers wherever applicable. It wasn't immediately clear to me that `prerender.js` and `assets.json` were both server-only. By adding the access...

> Alternatively, could we instead send those 2 to a `serverBuild` folder? Yes, that would be just as readable, and would pull it out of runtime.