superagent VS Bacon

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.

bacon.js

It would be awesome to develop something abstract and useful for usage as common PL (besides just solving specific problem), but it's really hard to develop a general purpose language (with memory management, mutations, etc.). For example, at my work I built reactive library mostly similar to Rx.js or Bacon.js, but with additional ability to compose different reactive systems on top of each other, so that streams declaration order won't matter and might be deployed separately while being glued at run-time (as long as stream names match). It's all cool, but system would only allow reactive functions (without imperativity and mutable objects), then the whole code would look really ugly and I definitely wouldn't be able to promote it among my colleges ^^, especially regarding how hard people migrate to new paradigms - sorry for complaining 😊.

Reactor is based on the same reactive principles as Bacon.js and Knockout.js.

Bacon.js - Functional reactive programming.

I remember hearing about Bacon.js one day and checking out their Getting Started page. In it, they demonstrate a counter using the Bacon event streaming library. This is the demo code: