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 🙏

© 2026 – Pkg Stats / Ryan Hefner

myoo

v0.0.19

Published

A simple implementation of functional reactive stream library for JavaScript

Readme

 _ __ ___ __  __ ___   ___
| '_ ` _ \  \/ /` _  \/ _  \
| | | | | |   /| (_| | (_| |
|_| |_| |_|__|  \___/ \___/

Make your own observables

This is my attempt to implement the ECMAScript Observable proposal

It is heavily inspired by the Ben Lesh's artice and RxJS.

One big difference to the RxJS is that RxJS uses the lift operator to create an observable and has far less (none?) closures.

Why?

Well I just want the truly understand Observables and thought the good way would be to implement them. This is very simple implementation and by far not complete. For the production you would probably want to use RxJS

Installation

ES6 via npm

npm install myoo

To import everything:

import * as Myoo from 'myoo/Myoo';

Myoo.Observable.of(1,2,3)

To import only what you need (Observable will be patched):

import {Observable} from 'myoo/Observable';
import 'myoo/add/operator/map';

Observable.of(1,2,3).map(x => x + '!!!'); // etc

To import what you need and use it with ES next function bind:

import {Observable} from 'myoo/Observable';
import {map} from 'myoo/operator/map';

Observable.of(1,2,3)::map(x => x + '!!!'); // etc

CommonJS via npm

npm install myoo

To import everything:

var Myoo = require('myoo/Myoo');

Myoo.Observable.of(1,2,3)

To import only what you need (Observable will be patched):

let Observable = require('myoo/Observable').Observable;
require('myoo/add/operator/map');

Observable.of(1,2,3).map(x => x + '!!!'); // etc

To import an operator and use it manually, do following:

var Observable = require('myoo/Observable').Observable;
var map = require('myoo/operator/map').map;

map.call(Observable.of(1,2,3), function (x) { return x + '!!!'; });

CDN

For CDN, you can use npmcdn:

https://npmcdn.com/[email protected]/bundles/Myoo.js

API

TODO

To be implemented

  • Observable.prototype [@@observable]()
  • Observable.from(x)
  • More operators (and tests)
  • Also use lift Operator concept to get rid of all those closures
  • Add hot observables (maybe based on another Ben Lesh's article

License

MIT