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

@infglef/ngrx-state

v1.3.0

Published

Schematics for ngrx state management

Readme

Ngrx-state functions

##Schematics:

Using init-state

Options:

name (The state name)
data (Boolean that determines whether to add a data level to the state)
container (Boolean that determines whether to add a container level to the state)
path (optional)
project (optional)
module (optional)

Created structure with all options true:

.
├── ...
├── statemanagement
│   ├── effects
│   │       └── {name}-root.effects.ts
│   ├── reducers
│   │       │── container
│   │       │    └── {name}-container.reducer.ts
│   │       │── data
│   │       │    └── {name}-data.reducer.ts
│   │       └── {name}-root.reducer.ts
│   ├── selectors
│   │       │── container
│   │       │    └── {name}-container.selectors.ts
│   │       │── data
│   │       │    └── {name}-data.selectors.ts
│   │       └── {name}-root.selectors.ts
│   └── state
│         │── container
│         │    └── {name}-container.state.ts
│         │── data
│         │    └── {name}-data.state.ts
│         └── {name}-root.state.ts
└── ...

The closest NgModule will then include imports of the ngrx modules StoreModule and if the effects option is checked the EffectsModule.

Using add-action

Options:

name (The action name)
path (optional)
project (optional)
module (optional)

Created structure:

.
├── ...
├── statemanagement
│   └── actions
│          └── {name}.actions.ts
└── ...

Using add-effect

Options:

name (The effect name)
path (optional)
project (optional)
module (optional)

Created structure:

.
├── ...
├── statemanagement
│   └── effects
│          ├─── {name}.effects.ts
│          └─── {name}-root.effects.ts      (This wil be created if it doesn't exist and the ngrx module will be added to the closest NgModule) 
└── ...

Using add-state

Options:

name (The state name) type (The type of state eg: container as seen in the init-state schematic)
path (optional)
project (optional)
module (optional)

Created structure with all options:

.
├── ...
├── statemanagement
│   ├── reducers
│   │       └── {type}
│   │             └── {name}-{type}.reducer.ts
│   ├── selectors
│   │       └── {type}
│   │             └── {name}-{type}.selectors.ts
│   └── state
│         └── {type}
│               └── {name}-{type}.state.ts
└── ...

Next to creating these files this schematic also adjusts the correlating root-reducer & state.ts

Using add-reducer

Options:

name (The reducer name) stateLevel (The state level name eg in init-state with data checked then you could use data as a value) className (The returned class of the reducer) array (boolean to make the return value of the reducer an array and not a single class) type (The type of state eg: container as seen in the init-state schematic)
actionType (optional) selector (optional) (boolean whether to add a selector) path (optional)
project (optional)
module (optional)

Created structure with all options:

.
├── ...
├── statemanagement
│   └── reducers
│           └── {stateLevel}
│                 └── {name}.reducer.ts
└── ...    

Depending on the options the stateLevel state will be adjusted to the return value. The stateLevel reducer will also be adjusted accordingly. If the selector option is true a selector will be added to the stateLevel selectors.

Using init-effects

Options:

name (The effects name)
path (optional)
project (optional)
module (optional)

Created structure with all options:

.
├── ...
├── statemanagement
│   └── effects
│          └─── {name}-root.effects.ts 
└── ...

The ngrx effects module will be added as an import to the closest NgModule

Using add-sandbox

Options:

name (The effects name)
importRootState (add rootState to constructor) path (optional)
project (optional)
module (optional)

Created structure with all options:

.
├── ...
├── sandbox
│   └── {name}.sandbox.ts
└── ...