got VS tinyhttp

I've used got, and my initial approach to this would have been to add a beforeRequest hook to strip a leading slash. I like the idea of handling this at compile time, though my proposed solution below (particularly the error messages) aren't the prettiest.

Like Python, our Node.js SDK is using a well-known library axios. While it is not quite as ubiquitous as Python's requests, it is very commonly used. For instance, it is used by Auth0 (if you're looking for a different example, Shopify makes use of Got). You can find it configured here. The shared client code takes reqeust and response transform functions for each resource to convert the repsonses to objects.

The properties/methods are also purposely used as a convention to work with responses in libraries like got, so by knowing Request and Response you will have sort of a "shortcut" in the learning process of open sourced tools.

Ah, yes, my apologies. I think the cause is that the latest version of got is not compatible with anything below node v14. I do see the error that you do when I have node v12 selected in my function service, but with v14 I'm able to deploy just fine. Do you still see that error when you click "Deploy" with Node v14 and got@latest?

Is there support for timeouts? It's the main reason I use https://github.com/sindresorhus/got

Things were working fine, and then my Blazor app started making calls to the server using a library called "Got" (https://github.com/sindresorhus/got)

At the moment, axios does not support setting a connection timeout separately from a read timeout, which could be limiting in some scenarios. If you need this functionality, you can try the got library - it allows for separate read and connection timeout specifications.

One of the community plugins we found during that process was signcl/docusaurus-prince-pdf, an npm package leveraging sindresorhus/got to crawl all the documentation and generate a PDF version.

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.