Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Would be great to have support for express 4 since strongloop is working on it, express continues its development.
Koa.js is good but I think it will require more work than express.js, and maybe until now is not so mature and well documented as express.js.
For now I will use sails with express.js 3.x but hopefully the core team include express.js 4 in upcoming releases.
And thanks to Sails's core team for their work, is really appreciated :)
@garysui if you're still experiencing compatibility issues, would you mind elaborating in a new issue with some specifics?
@andyhu using the dependencies of express 5 directly as discussed at that link ^^ would be an important first step towards this sort of thing. (Koa is possible-- however Hapi would be trickier because of the larger differences between its method names and functionality-- whereas Koa bears many more similarities to Express). In the mean time, if you're a Koa aficionado, you might check out Strapi by @loicsaintroch.
@mikermcneil hapi is great to use. It features strong validations (joi) and its architecture is modular. It also is battle-tested; see who's using it (http://hapijs.com/community). After the recent events (I'm averse to politics), I decided to switch from sails to hapi... (it was easy because I was using sails as an api backend). I've looked at Koa; it's great, but it looks like you could use hapi for a lot of stuff and build the MVC on top of it and have something really nice. Sails would be the icing on the hapi cake (if done right).
Just a note to say I'm grateful for sails and it has been a great tool to start using node.
Express 3.x IS NO LONGER MAINTAINED
I would strongly suggest to switch from Express 3 which may have security issues that are no longer researched nor maintained. To my understanding, security is a feature that a framework should ensure to its best.
Just my 2c, I talk too much and I should probably go back coding.
@devnomad glad to hear Sails has been helpful for you and best of luck :)
To clarify what's going on w/ Express 3, here's a relevant quote from the discussion in the link above:
There's more discussion on why we've made the decisions we have w/ Express 4, what's going on w/ Express 5, and our plans for jshttp/pillar in the linked PR.