Ts.ED VS Express

Ts.ED - Controller-based (DI supporting) backend framework that seems to offer quite a lot (although I'm wary of it being quite close to Nest.js)

Take a look at ts.ed. They have some similar feature

has anyone looked at tsed.io

As a developer, it's always important to find ways to streamline the development process and save time. For the past two years, I've been using Ts.ED as the framework for all of my applications and it's been a game-changer. Not only has it allowed me to gain back lost development time, but it's also been the foundation for my open-source project HighScore.

I use Ts.ed as framework, go to this site to known more about this awesome framework.

Because of this, I decided to create a base template of a REST API created with NodeJS, using Ts.ED as the base framework and TypeScript as the programming language. This template tries to follow the principles of Domain Driven Design and implements a Clean Architecture/Hexagonal Architecture to try to rely as little as possible on the infrastructure and the framework while keeping in mind at all times the language and the needs of the business logic.

I love Ts.ED https://tsed.io

I'd also love to shout out Ts.ED which is another great Typescript framework that I've written production applications with. It's a natural fit for anyone who loves .NET applications, it's why I chose it.

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...

ExpressoTS fully supports Express middleware.