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

@aicacia/state

v0.2.8

Published

state management for applications

Downloads

39

Readme

ts-state

license docs npm (scoped) build

state management for applications

Introduction to State

This library handles state a little differently than you might be accustomed to in your day-to-day frontend development, especially if you do a lot of coding with Redux. To some extent we like Redux, at least we like the features it offers such as having an immutable application state and allowing for a way to walk through and replay changes in your application. However, for our purposes it is too verbose and makes the developer think about things that they should not care about. The developer should only worry about his application such as building a login form or a sign in page and not about how to manage a full update cycle of application states and dispatch events for various components.

Library Design Goals

What we have tried to achieve with this library is the following architectural design goals.

  1. Provide all the features of Redux.
  2. Reduce the amount of code required to manage state in frontend applications.
  3. Reduce the amount of cognitive overhead required.
  4. Make building your applications less about state and more about the features of the application.

State and Stores

a State is the single source of truth for applications, states can have views which are slices into your state that are used to update the main state.

Example Store

const TODO_LIST_NAME = "todo_list";

interface ITodo {
  id: number;
  text: string;
}

interface ITodoList {
  list: ITodo[];
}

const todoListInitalState: ITodoList = {
  list: [],
};

function TodoListFromJSON(json: IJSONObject): ITodoList {
  return {
    list: (json.list as Array<IJSONObject>).map((json) => ({
      id: json.id as number,
      text: json.text as string,
    })),
  };
}

const state = new State(
  {
    [TODO_LIST_NAME]: todoListInitalState,
  },
  {
    [TODO_LIST_NAME]: TodoListFromJSON,
  }
);

const todoList = state.getStore(TODO_LIST_NAME);

const createTodo = (text: string) => {
  const id = createId();

  todoList.update(
    (state) => ({
      ...state,
      list: [...state.list, { id, text }],
    }),
    "create"
  );

  return id;
};

const removeTodoById = (id: number) =>
  todoList.update((state) => {
    const index = state.list.findIndex((todo) => todo.id === id);

    if (index === -1) {
      return state;
    } else {
      const newList = state.list.slice();
      newList.splice(index, 1);
      return { ...state, list: newList };
    }
  }, "remove");