got VS ipfs

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.

I don't mind pinning, but back in the day I was having issues using IPFS to transfer small files between devices. I admit I haven't investigated to see if the problems were ever resolved.

I've been watching https://github.com/ipfs/helia which is going to replace https://github.com/ipfs/js-ipfs and hoping they can get an IPFS node working in the browser.

I haven't tried https://js.ipfs.tech/ (js-ipfs) in a while, what is the state of it?

On the topic of IPFS, but also slightly tangential -- how has nobody written an Activity Pub client/server in Javascript and distributed it as a Browser Addon?

If IPFS can be literally hosted via a Firefox Extension[1], how has nobody done the same for an arguably easier protocol like Activity Pub?

1: https://github.com/ipfs/js-ipfs

If you can load them up in js-ipfs that might be better?

Store the content in ipfs and just put the hash in the URL? I haven't used https://github.com/ipfs/js-ipfs in this capacity but I'm under the impression that that's what it's supposed to do.

js.ipfs.tech

You need an import statement instead of require since Node has upgraded to the new module system. Use import * as IPFS from 'ipfs-core'. Read more here: https://github.com/ipfs/js-ipfs

Please take a look at https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/FILES.md for more understanding

You could include js-ipfs[0] and fetch all your resources from IPFS without going through a gateway. However, this approach would make the site fully dependent on JavaScript.

A PWA with a Service Worker could perhaps implement its own client-side "gateway", translating public gateway URLs into direct IPFS access. Without the Service Worker (or without JS) it would fall back to using the gateway.

[0] https://js.ipfs.io/

Of course,You can try it out. You can create some Hash to IPFS from this link Adding data to IPFS https://js.ipfs.io/ and then browse the hash in https://ipfs-gateway.cloud/ It is directly connected to IPFS Node.