SailsJS VS Nodemon.io

Sails is a realtime JavaScript framework built on top of Express. Sails offers built-in realtime communication support and a flexible routing system.

Community stats: Sails GitHub repository has an active community with 22.78k stars and 2k forks. They also have a YouTube channel with a library of useful tutorial videos.

Sails.js: Sails.js pitched itself as the MVC framework for Node.js, bringing a Rails-like experience while being database agnostic.

Disclaimer: I didn't know much about Websockets 1 week ago, all the experience I had with Websockets was when I developed a chat application back in 2016 using a JS framework that tried to be a Ruby on Rails implementation called SailsJS, so I decided to research about this technology and consumed multiple resources which I will link in this blog post and each section.

Perhaps Sails.js. They mention RoR. An Angular teacher used it to create a fast API.

I was just talking about this topic of whether we really has any Rails-influenced JS frameworks out there in the wild. And I struggled to come up with anything off the top of my head other than Sails.js [1]. RedwoodJS looks interesting, what about it in particular do you find exciting?

[1] https://github.com/balderdashy/sails

Sails JS – The MVC framework for Node.js

First hurdle. ExpressJS isn't a great framework on it's own for building web sites. You need to cobble together some combination of a view engine, templating etc otherwise out of the box you'll end up handcrafting HTML which I don't think is what you want right now. I'm not up on the latest server-side web frameworks and don't think now is the time to get into react + nodejs. So I'll just suggest Sails: https://sailsjs.com/. Follow their intro guides to get yourself a basic website with text entry.

nodemon - enables automatic reload of your server after code change docs

Then, install nodemon (in the VSCode terminal also), which, to my understanding, automatically refreshes the server you'll be sending requests to, whenever you make a change. Using plain node.js, you'd have to manually stop and restart the server after every change.

That's already pretty good, but as you already know it's a PITA to work with this during development. You will have to rebuild your Docker images whenever you change your code, even though your apps will probably support hot-reloading out of the box (or with something like Nodemon if not).

Are you moving your projects to use ES Modules but you are facing some unexpected issues? You are not alone in this fight. In this tutorial, you will learn how to set up nodemon along with ts-node.

We can now use npm run dev to start the server using nodemon, which enables hot refreshing on changes.

Welcome to my blog, where we dive into the intriguing world of Node.js development and tackle one of the common stumbling blocks many developers encounter: the "Nodemon Error - nodemon.ps1 cannot be loaded because running scripts is disabled on this system." If you've ever come across this error while working with Nodemon, fear not! In this article, we will explore the causes behind this issue, understand why scripts are disabled on certain systems and most importantly, provide you with practical solutions to overcome this obstacle and keep your development workflow seamless. So, let's embark on this troubleshooting journey together and empower ourselves to conquer the Nodemon Error!

You’ll need to restart the server using node index.js whenever you change any project file. You can also use Nodemon to automate this.

nodemon will be required to monitor for any changes in our source code and automatically restart our server.