0

Has anyone used sails.js ? Any strong-suites and/or pitfalls I should be aware of going in?

Comments
  • 0
    Quit using it because no typescript support and the syntax it uses for endpoints is just garbage, now using https://nestjs.com/ it makes use of the new ES features. And more customisable but that with trade-off for more setup. So it really depends what your use case is. I've used sails when 1.0 was still in heavy development and they were still transitioning allot of their documentation so that wasn't that great. After looking back today at what it has become today it looks like they are trying to stay too backwards compatible. But then it comes back to what is your use case. 🙃
  • 0
    @badgamernl im looking over nexts documentation and im wondering ok wheres the controllers, actions, services, models? The pieces of a backend framework that help me maintain sanity. Next looks like a javascript version of good old fashion php. The documentation title "Fetching data for pages" utilizes a method to fetch props from an external API. Im looking for a server side node solution that will handle a high volume of traffic and database lookups. I feel like modern web frameworks were created to avoid the direction next is headed back into
  • 0
    Very nice node framework, just take note of views and your data bindings
  • 0
    @devJoe I was actually going to use it as its own micro service and have a separate react app utilize it. Is it easy to use react as a front end with sails?
  • 0
    Tried it with ejs and was ok, you can give it a go!
  • 0
    @dUcKtYpEd not sure what you are saying there, I was referring to another package
  • 1
    @badgamernl oh shoot that’s funny. Just shows you how many node libraries there are
Add Comment