Need explicit connect requirement

Open jessesanford opened this issue 14 years ago • 2 comments

Now that connect has just been upgraded to 2.0 this library needs to be tested for forwards compatibility. I have set the connect requirement explicitly to make sure it does not break when doing an npm install.

Feb 28 '12 18:02 jessesanford

@jpallen, I'm having deployment problems in production because of this as well.

Feb 28 '12 21:02 c4milo

I also ran into this today. I think the better solution is to figure out why it's failing on on the 2.0 branch and fix it so it works on there.

Mar 01 '12 07:03 brianloveswords