got VS Guzzle

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.

Guzzle is a PHP HTTP client library. It’s a simple and effective solution for sending HTTP requests and managing HTTP/1.1 and HTTP/2.0 responses. This versatile tool excels in several areas, allowing developers to build query strings quickly, send POST requests, upload JSON data, and handle other HTTP-related tasks. Moreover, Guzzle facilitates both synchronous and asynchronous request handling, providing flexibility for different scenarios.

Symfony HTTP Client or Guzzle. If new build then Symfony, but have a lot of existing implementations with Guzzle. Both have worked very well. Worst case fallback to cURL.

but if you'd rather make raw requests, guzzle is a good option (though I'd opt for the sdk): https://github.com/guzzle/guzzle

PHP has built-in cURL support, but I never use it. I like using Guzzle or Symfony's http-client.

I just ran into multiple errors regarding the pre-packaged cURL: It does not feature accepting compressed responses (which I suppose is due to absense of `libz` being compiled/linked in).

I am busy building a small application that monitors websites using guzzle. My idea is to run through the list of websites alphabetically and make a guzzle request to each and update my table with the http response codes of each site.

Like Node.js, the PHP ecosystem has quite a number of good HTTP request libraries. Guzzle is perhaps one of the most well known, but there are many other popular libraries out there. Luckily, PHP also has some interface standards around HTTP clients and messages, particularly PSR-7, PSR-17, and PSR-18,