backend-server VS tinyhttp

I’ve been working on eaf-linter for about a few days now, and it already has 6 stars and 2 forks. My other project that I've been working on, the Backend Server, has 14 stars, 9 forks, and nearly 10 outside contributors. That might not sound like a lot, but both of these projects are only about a week old.

I’ve been working on my open-source backend server for about a week now, and it already has about 12 stars, 9 forks, and nearly 10 outside contributors. That might not sound like a lot, but the project is only a week old and it isn’t a package or anything that can be used by outside people.

Here was the project if you want to check it out

I’ve been working on building a non-profit, open-source organization for a while now and we have gotten to a solid point in the backend code. We have authentication, an event and rsvp system, profile picture generator, etc. If you want to check it out, you can here.

If you want to check out the code for the project, it’s all publicly available here. Make sure to star the repository!

I decided to drop everything that I was doing and build a really simple API for duck jokes. Right now the API has a couple of jokes, but we need some more, so if you want to submit some, you can respond to this issue or you can just drop a pull request on this repository.

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.