superagent VS ipfs

SuperAgent is a lightweight and flexible HTTP client that supports promises and callback-style syntax. It is known for its simplicity and ease of use.

You’re putting together an npm library that involves fetching data. There are many popular packages that can help you (axios, superagent, etc.) but in the spirit of not shipping bulky/redundant JS code to the browser, and the progress which browsers and JavaScript has made over the years, you try to use the platform whenever possible.

You are using Superagent and RSS parser to get the task done. Superagent and RSS parser both support callback and the Promises API (coming up next). If this code was written for the backend with Node.js, we wouldn't need the CORS proxy. It is needed for the frontend.

There is a part Api.fetchUser that is not explained, thus I don't quiet understand if that is something we need to handle with libraries like axios or superagent? or is that something else. And are saga effects like call, put etc.. equivalents of get, post? if so, why are they named that way? Essentially I am trying to figure out a correct way to perform a simple post call to my api at url example.com/sessions and pass it data like { email: 'email', password: 'password' }

Create your new project and install our lone requirement [superagent](https://www.npmjs.com/package/superagent), an HTTP client library to make HTTP requests in Node.js, by running:

SuperAgent (https://github.com/visionmedia/superagent)

Superagent is a great tool for testing API’s, you could use something like Postman, but combined with Jest you can accomplish a lot.

We will be using SuperAgent for making API requests, so let's add it to our dependency list. yarn add superagent Next, we will create a routes/__layout.svelte file, which will wrap around any of the routes in the directory.

Route tests are tests that actually call endpoints in the apis and tests for the happy path and sad paths. Supertest is the package for write route test. Supertest is built on superagent, which is an HTTP request library. So your Express app is actually called like if a user was making a request

superagent - HTTP request library.

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.