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

lcars

v1.1.1

Published

A queued flux dispatcher

Downloads

44

Readme

LCARS

LCARS

A queued flux dispatcher

Demo [source] [live demo]

Install

npm install lcars

Usage

LCARS is a dispatcher that uses facebook's flux dispatcher. We are not re-creating our own version of flux, but providing some of the implementation details you might need to get started with flux.

It is common in flux applications to have one dispatcher. That is how we use it, but in practice, you could have more than one. We feel to follow flux, and to make your application easier to follow, it is a good practice to only have one. Be cautious of this. Please read this if you havent yet.

The place that dispatchers are mostly used is in your Action Creator and Stores.

Example

# /actions/HelloWorldActionCreator.js

var LCARS = require('lcars');
var HelloWorldConstants = require('./../constants/HelloWorldConstants');

var HelloWorldActionCreator = {
  updateAge: function(data){
    LCARS.dispatch({
      type: HelloWorldConstants.DemoActions.SET_AGE,
      data: data
    })
  }
};

module.exports = HelloWorldActionCreator;

When you call HelloWorldActionCreator.updateAge({age: 30}), your dispatcher (LCARS) will register callbacks that you can respond to.

# /stores/HelloWorldStore.js

'use strict';

var LCARS = require('lcars');
var CargoBay = require('cargo-bay');
var HelloWorldConstants = require('./../constants/HelloWorldConstants');
var merge = require('amp-merge');

var HelloWorldData = {
  _data: {
    name: "Bob",
    age: undefined
  },
  clonedData: function() {
    return JSON.parse(JSON.stringify(this._data));
  }
};

var _setAge = function(age){
  var data = HelloWorldData.clonedData();
  data.age = age;
  HelloWorldData._data = data;
  return HelloWorldData.clonedData();
};

var HelloWorldStore =  merge(CargoBay, {
  getDataFromStore: function(){
    return HelloWorldData.clonedData();
  }
});

HelloWorldStore.dispatchToken = LCARS.register(function(action){
  switch (action.type){
    case HelloWorldConstants.DemoActions.SET_AGE:
      _setAge(action.data.age);
      HelloWorldStore.emitChange();
      break;
  }
});

module.exports = HelloWorldStore;

You can see an example of this in freighter.

To contribute


npm install

npm test