connect VS resty

connect.multipart() will be removed in connect 3.0visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternativesconnect.limit() will be removed in connect 3.0Express server listening on port 3000 The app works, that's fine. But when I clone an app created in other computer I don't get that message, so I'm supposing I have something outdated in my computer.

Right now you're thinking "but this doesn't support middleware, how would I enable cors?" Well, resty is just a good old request handler, so you could actually combine it with connect.

Express GraphQL is a library for building production ready GraphQL HTTP middleware. Despite the emphasis on Express in the repo name, you can create a GraphQL HTTP server with any HTTP web framework that supports connect styled middleware. This includes Connect itself, Express and Restify.

Last week I published two packages on NPM. One (resty) depends on the other (typed) but typed can be used standalone. Resty is a simple, type-safe, radix-tree based library for building small and simple RESTful APIs. Typed is a 1kb runtime type-checking library perfect for validating and type-casting JSON data. I use both on personal projects but I would love some feedback from the community to make them rock-solid. Hope somebody find them useful.

A few days ago I posted about a library I made called typed and it never happened to me before that people would actually use something I made. The thing is that I made typed to be a companion library to resty which is a thin wrapper around Node's http core module.