tinyhttp VS Express

After this I really hit the ball rolling and was able to find more issues to work on. One thing that I enjoyed was that all of my PRs were drastically different from each other. I worked on correcting documentation for AdonisJS, fixed a HTTP Content-Type Header bug in tiny-http, and then finally even created a short script for users to load up their own local version of the Electron documentation site.

I worked on Issue 360. Essentially, when a user would set the "Content-Type" header before returning the file, the framework would overwrite the "previous" header, with the type that it determined from the files type.

tinyhttp: a modern web framework written in TypeScript. It uses tsm in its documentation examples as a simple way to get users up and running quickly

The framework I decided to use today was tinyhttp, with an API similar to Express, I don't have a specific reason to use this framework and the example code is easily replicated to other frameworks.

Now, we will create API using expressjs. When we created application using --ssr flag, the Angular CLI already took care of installing expressjs for us.

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.