npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

rx-http

v0.2.0

Published

An minimal http library built on Rx and core Node libraries

Downloads

5

Readme

Rx http (WIP)

This library was written to wrap the core Node.js http library in Rx observables. It also enforces a lot of opinions on your requests. I don't expect it to work for all use-cases. Mostly it serves a very similar need as a promise. The benefit gained from using Rx around http calls comes when you start writing requests that need to be repeated many times, or need to be chained with other Rx-isms. The Rx semantics allow you to write your programs more declaratively.

This is one of my attempts at finding how much observables can replace other idioms in my code.

Docs

Each method returns an Observable and may emit an event on either the next, error, or complete channels.

getJson$

var rxHttp = require('rx-http');

rxHttp.getJson$('http://example.com/user/1').subscribe(function(obj) {
  // do something with `obj`
});

rxHttp.getJson$('http://example.com/user/1').subscribe(
  function(obj) { /* next */ },
  function(err) { /* error */ },
  function() { /* complete */ }
);

postJson$

rxHttp.postJson$('http://example.com/user', {name: 'jon'}).subscribe(function(obj) {
  // do something with `obj`
});

Tests

This code is unit tested with mock http calls.

npm test