Status of Sails.js

Re:Status of Sails.js by delbel on Thursday December 31, 2015 @09:17PM (#10820851)

Currently a week or two in on a new project using Sails. Any alternatives? Originally, I was going to use just Hapi + Sequalize. Thanks

[ Parent | on HN ]

Re:Status of Sails.js by connor4312 on Friday January 01, 2016 @02:11AM (#10821323)

We ported from Sails to Hapi and Sequelize several months ago. The issues with Sails have been covered exhaustively. (Finding a third SQL injection vulnerability in the default behaviour of Sails+Wuterline, as we lovingly nicknamed it, was the final straw for us.) We have zero regrets.

[ Parent | on HN ]

Re:Status of Sails.js by traviswebb on Thursday December 31, 2015 @10:37PM (#10821027)

FWIW, Trails.js is based on hapi, and we will be adding Sequelize support after 1.0-beta is released in February.

[ Parent | on HN ]

Re:Status of Sails.js by qaq on Thursday December 31, 2015 @09:36PM (#10820886)

Hapi+Bookshelf :)

[ Parent | on HN ]

Re:Status of Sails.js by sergiotapia on Friday January 01, 2016 @12:41AM (#10821192)

Meteor - it's webdev that doesn't suck.

[ Parent | on HN ]

Re:Status of Sails.js by uptownJimmy on Friday January 01, 2016 @07:56AM (#10821764)

It's webdev that doesn't support a properly robust db. When they finally fix that Achilles' heel, they might have a chance of lasting long-term. MongoDB is not gonna cut it.

[ Parent | on HN ]