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

ptw-store

v1.1.0

Published

A RxJS powered state management container heavily inspired by Redux.

Downloads

1

Readme

PTW-Store

Build Status npm version

A RxJS powered state management container heavily inspired by Redux.

Why!?

Because reactive by default is a good thing and Redux is too much tied to React! Plus, we wanted to have some sensible defaults, like FSA for actions.

Features

  • Same API: We tried to stay compatible with the Redux API, so existing middleware and other plugins will work as expected!
  • Observable State: The store will also expose a state$ stream, which is just a regular Observable. This means you can use all the sweet Rx operators!
  • Real State Change: Redux will always call every listener, when an action is dispatched. Because of RxJS listener will only be notified if the state has actually changed.
  • Partial State Update: Sometimes you're only interested in a subset of the state tree. select() is a helper method, exposed by the store to easily select state members, much like @ngrx/store.
  • Framkework Agnostic: Use it for whatever you want.
  • Intellisense: Thanks to TypeScript.

Install

$ npm install rxjs ptw-store --save

Usage

import { Action, Reducer, createStore } from '@ptw/store';

/**
 * This may look familiar!
 * Reducers have a generic type, which helps to keep track of
 * the state a reducer mutates.
 */
const counter:Reducer<number> = ( state=0, action ) => {
    switch(action.type) {
        case 'INCREMENT':
            return state + 1
        case 'DECREMENT':
            return state - 1
        default:
            return state
    }
};

/**
 * Generics indicate the type of the state (=`number`) and the allowed
 * types of actions that can be dispatched to the store (=`Action`).
 */
const store = createStore<number, Action>(counter);


/**
 * Subscribe directly to the observable or do a regular subscription.
 * NOTE: Unlike Redux listeners will be called with the current `state`. But
 * you can always fall back to `getState()`.
 */
store.subscribe( state => console.log(state) );
store.state$.subscribe( state => console.log(state) );

/**
 * Dispatch as usual.
 */
store.dispatch({ type: 'INCREMENT' });
store.dispatch({ type: 'INCREMENT' });
store.dispatch({ type: 'DECREMENT' });

Combine Reducers

import { Action, combineReducers, createStore } from '@ptw/store';

/**
 * Combining reducers works much like it does with Redux.
 */
interface Counter {
    counter?:number;
    stack?:string[];
}
const reducer = combineReducers<Counter>({
    counter: (state = 0, action) =>
        action.type === 'increment' ? state + 1 : state,
    stack: (state = [], action) =>
        action.type === 'push' ? [ ...state, action.payload ] : state
});

/**
 * In this case the reducers also define the store's state.
 */
const store = createStore<Counter, Action>(reducer);

/**
 * Yay, autocomplete!
 */
const current = store.getState();

With Middleware

import { applyMiddleware, createStore } from './src/index';
import thunk from 'redux-thunk';
import reducer from './reducer';

/**
 * Aplly middleware like you're used to.
 */
const store = createStore(
    reducer,
    applyMiddleware(thunk)
);

Scripts

  • Build: npm run build
  • Test: npm run test
  • Develop: npm run watch

ToDo

  • Integrate ImmutableJS as state.