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

ngrx-fsm

v1.0.4

Published

**NGRX BASED FINITE STATE MACHINE**

Downloads

15

Readme

ngrx-fsm

NGRX BASED FINITE STATE MACHINE

This library was generated with Nx.

Creating a Finite State Machine for handling component state in an Angular app.

We were finding the use of boolean flags to dictate which state a particular component was in was ok at a very simple level, but as the app grew, and more complex components were added, it didn't scale well.

What we wanted was a way of components registering a map of valid transitions. Then as actions are emitted they are checked against this map. If valid, the components current state is updated in a special UIState slice of the store and the action is passed trough. If not a valid transition for the given component the action is dropped. For example:

  • An 'Add Book' component, can be in a state of Idle, Processing, or Errored
  • An AddBookAction causes it to transition from Idle to Processing.
  • This transition is only allowed if the component is currently Idle. If the component is Processing then the transition should be disallowed

🎰 Working with a state machine

📦 Installation

We recommend using @angular/cli to install. It not only makes development easier, but also allows you to take advantage of the rich ecosystem of angular packages and tooling.

$ ng new PROJECT_NAME
$ cd PROJECT_NAME
$ yarn add @ngrx/store
$ yarn add ngrx-fsm

Provide the and NgRx ActionsSubject ComponentStateBuilder

import {
  COMPONENT_STATE_FEATURE_KEY,
  ComponentStateBuilder,
  ComponentStateFacade,
  ComponentStateMachine,
  componentStateReducer,
  ComponentStateService,
} from 'ngrx-fsm';

bootstrapApplication(AppComponent, {
  providers: [
    provideStore({
      [COMPONENT_STATE_FEATURE_KEY]: componentStateReducer,
    }),
    ComponentStateFacade,
    ComponentStateBuilder,
    ComponentStateService,
    { provide: ActionsSubject, useClass: ComponentStateMachine },
  ],
}).catch((err) => console.error(err));

Fluent style builder setup for a given component


// With the fluent builder, component states can be specified like this ...

const componentStates = this.componentStateBuilder
    .create('userApproval')
    .forAction(actionTypes.loadUnapprovedUsers)
    .fromState(ComponentStates.Idle)
    .toState(ComponentStates.Processing
        .passThrough()
        .forAction(actionTypes.loadUnapprovedUsersSuccess)
        .fromState(ComponentStates.Processing)
        .toState(ComponentStates.Idle)
        .passThrough()
        .forAction(actionTypes.loadUnapprovedUsersError)
        .fromState(ComponentStates.Processing)
        .toState(ComponentStates.Idle)
        .terminate()

// the component uses an injected componentStateService to register its state transitions

this.componentStateService.addComponentStates(componentStates);

Demo was a better approach

So, run showcase project on stackblitz WIP you can clone a repo then:

Run yarn start to execute the showcase demo.