saas-express-starter-kit VS Express

So I have been working on a SaaS starter kit - a boilerplate code for a SaaS app, using node and express. Now that it has become useful to some people and the code is growing, I want to make sure thag the developer experience is not lost in an attempt to add more features. I thought having a clear project goals with principles(e.g. no opinion about styling) to follow will help with this. So here I have written down the goals and the principles that will make DevX better, need your feedback what other principles should I add? TIA

Best comment on how to structure your web app. There's a GitHub repo with boilerplate to follow this pattern

Agree. And that's where express boilerplate such as saas-express-starter-kit can become handy.

How will we do it within a week? We will use this starter kit template to start with common things structured and built out of the box (e.g. auth, email, events, etc.)

I choose Express, always. To speed up further, use the boilerplate - https://github.com/makeitcount/saas-express-starter-kit

It won't be a small discussion. Let's discuss this on the GitHub repo issues

First, we import express. The Express framework allows us to create routes that will respond to webhook POST requests and serve an HTML file when a GET request is made to the root of the site.

Basic Knowledge of Express

Express.js Documentation

In the JavaScript ecosystem, there are guides for enabling SAML-based enterprise single sign-on in AdonisJS, Express.js, Next.js, Remix, and React with an Express.js backend.

Starting off strong with Express.js, the cool kid on the block for building web apps. It's lightweight, flexible, and doesn't throw a tantrum when you ask it to scale. With Express, you can handle HTTP requests like a pro, play around with middleware, set up routes without breaking a sweat, and render views that make your app look stunning. Big names like Netflix and Uber are already on board, and if it's good enough for them, it's definitely worth a peek.

express - one of the most popular middleware tools, lightweight and easy to learn. docs

Now we can install both Express and Socket.io libraries:

app.listen(3000); ``` Now you can run your server by executing `node index.js`. Your web application will be accessible at http://localhost:3000/, where you'll see "Hello, world!" displayed in your browser. Congratulations! 🎉 You've successfully set up basic routing with Express.js! This guide covered only the tip of the iceberg when it comes to utilizing Express.js features. Explore its extensive documentation (https://expressjs.com/) to discover more possibilities. Remember, with Express.js, you have the power to build efficient and scalable web applications. Happy coding!

Converting a large Express.js application from JavaScript to TypeScript can be a challenging task. For many applications, this represents a significant portion of their technical debt, as the process may span many days, if not months, and new changes are typically not allowed during the conversion.

Nitro is a nice https webserver that you can deploy everywhere. Comparing it to express, it doesn't need weird middlewares for json, it has a simple way to support caching, a file system router, tasks and scheduled tasks that avoid quite a few shell scripts, db:migrations etc, plugins, KV storages, SQL connectors, websockets...