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

pyx

v0.2.0

Published

A class-based flux implementation.

Downloads

7

Readme

Pyx - a Flux implementation

Synopsis

const Pyx = require('pyx')

class SimpleStore extends Pyx {
  constructor() {
    super()
    this.status = '' // or call this._resetProps()
  }

  _resetProps() {
    this.status = ''
  }

  props() {
    return [ 'status' ]
  }
}

At this point, all functionality in Pyx is complete. You may also override other methods such as _resetStores if you need to do something different instead of just calling .reset() on all sub-stores. e.g. if you don't want to reset a specific sub-store.

You may also override reset, extract and restore if you need to do something different with these too.

Why this Flux Implementation?

The main reason I like using this is because each store and sub-store knows exactly what it is doing. There is no indirection between event dispatch and the store - just call the event on the store itself.

It also help in being able to get sub-stores from top-level stores and pass those on to each React component individually instead of having to pass the entire store down. I have found that many times, a component and a store go hand-in-hand and then sub-stores and sub-components do the same.

Author

Andrew Chilton.

License

ISC.