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

@cobuildlab/flux-state

v1.2.2

Published

A Easy State Management with Flux

Downloads

139

Readme

Flux State

Learning flux is hard, using it is cumbersome. Hopefully it will become easier with this library!

Also, learning redux is harder, so this is state library that make your life easier

The principles and guidelines supporting this Library are:

  1. Define a Store should be an easy step, keeping the power of a "Single source of truth"
  2. Data and event propagation should be done in a declarative way
  3. Views should be developer in a reactive way.
  4. Multiple Stores are allowed for better organization
  5. We keep flux as it should be unidirectional, so there is no coupling between the Action and the Views, neither between the Actions and the Store, neither between the Store and the View
  6. The Store state is implicit: The last value of all the events on the Store.

Installation

  1. Run on your terminal the following command:
$ npm install @cobuildlab/flux-state --save
  1. To import the library anywhere you would like to use it:
import Flux from '@cobuildlab/flux-state';

Let's build a Flux Workflow for authentication

1) First, declare your Store

import Flux from '@cobuildlab/flux-state';

export const LOGOUT_EVENT = 'onLogout';
export const LOGIN_EVENT = 'onLogin';
export const SESSION_EVENT = 'onSession';
export const NEW_EVENT = 'onEvent';

class SessionStore extends Flux.DashStore{
    constructor(){
        super();
        // Declare an Event
        this.addEvent(LOGOUT_EVENT);
        // Or Declare an event with some immutable transformation logic
        this.addEvent(LOGIN_EVENT, (state) => {
            // Do something with the data before propagating the Event
            return Object.assign(state, {"key": "value"})
        });
        // Or Declare an event with some plain transformation logic
        this.addEvent(SESSION_EVENT, (state) => {
            state.some_other_property = "Some other Data";
            return Object.assign(state, {"key": "value"})
        });
        // You can also provide initial Value to  the events
        this.addEvent({eventName: NEW_EVENT, reducers:[], initialValue: {foo: 'bar'} });
    }
}

const sessionStore = new SessionStore();
export {sessionStore};

2) Registering with the Store changes

import React from 'react';
import {sessionStore, LOGIN_EVENT, LOGOUT_EVENT, SESSION_EVENT } from '/path/to/store';

export class View extends React.Component {
      constructor(){
          super();
          const user = sessionStore.getState(SESSION_EVENT);
          this.state = {
            isLogged: !!user
          }
      }

      componentDidMount() {
          this.loginSubscription = sessionStore.subscribe(LOGIN_EVENT, (state) => {
              // Do something useful with the Event Data
              this.setState({some: state.some});
          });
          // Register some method
          this.logoutSubscription = sessionStore.subscribe(LOGOUT_EVENT, this.logOutEvent().bind(this));
      }

      componentWillUnMount() {
          // Don't forget to release the subscription
          // Save time by using react bindings
          // See (react-flux-state)[https://github.com/cobuildlab/react-flux-state] 
          this.loginSubscription.unsubscribe();
          this.logoutSubscription.unsubscribe();
      }
  }

3) Define some actions that will trigger the event

import Flux from 'flux-state';
import {LOGIN_EVENT, LOGIN_ERROR} from '/path/to/store';

const authenticateAction = async (username, password)=> {
      // Don't forget to Validate the data ex: username !=== undefined
      let dataToSave = {
          authenticated: true
      }
      
      try {
        await authenticate(username, password)
      }catch (e) {
          Flux.dispatchEvent(LOGIN_ERROR, e.message);
      }
      Flux.dispatchEvent(LOGIN_EVENT, dataToSave);
}

export {authenticateAction};

4) Glue all together using the Action from the View

import React from 'react';
import {authenticateAction} from 'path/to/action';
import {sessionStore, LOGIN_EVENT, LOGOUT_EVENT, SESSION_EVENT } from '/path/to/store';

export class View extends React.Component {
      constructor(){
          super();
      }

      componentDidMount() {
          const me = this;
          this.loginSubscription = sessionStore.subscribe(LOGIN_EVENT, (state) => {
              // Do something useful with the Event Data
              me.userName = state.user.name;
          });
          // Register some method
          this.logoutSubscription = sessionStore.subscribe(LOGOUT_EVENT, this.logOutEvent().bind(this));
      }

      logOutEvent(state){
        //DO something with the state or the state of the Store
        const storeState = sessionStore.getState(SESSION_EVENT);
      }

      componentWillUnMount() {
          // Don't forget to release the subscription
          this.loginSubscription.unsubscribe();
          this.logoutSubscription.unsubscribe();
      }

      login(){
        authenticateAction(this.state.username, this.state.password);
      }

  }

ChangeLog:

v 1.2.1

  • add addFluxEvent to the store, to provide initialValue
  • add addFluxEvent to the store, to change transformers for a most common name: reducers
  • add addFluxEvent to the store, to provide named parameters

v 1.1.5

  • Notification for events are now clones from original Data

v 1.1.4

  • Rollback of async dispatches: They will stay sync for now

v 1.1.3

  • Now Flux.dispatch uses setTimeout to avoid dispatching in the middle of a Dispatch

v 1.0.1

  • store.getState() returns a clone of the state object
  • Migrated to @cobuildlab/flux-state

v 0.0.3

  • Add a clearState method for the Store to set all Values to null
  • Add a parameter to the subscription, to request the last value of the Event if wanted
  • Add a Helper React View, to subscribe and unsubscribe to the Store wanted

Contributors