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

@liamzebedee/stateman.js

v0.1.0

Published

stateman.js ===========

Readme

stateman.js

A tiny (60 LOC), simple, state management library for React.

Install.

npm i stateman.js

What is stateman?

Stateman is basically the ViewController pattern for React. It's extremely simple and straightforward. You define a class that has state and methods (mutations like addTodo, getters like getTodo, async too).

Unlike other state management solutions, stateman is basically plain JS. There are no new patterns to learn, there's no special syntax, there's no boilerplate. Stateman looks like regular JS, and it's only 60 lines of code with no external libraries.

It's really easy to define controllers, and then use their state in different places. There's no Context, there's no deep copying or performance overhead.

Let me show you:

Define controllers. Controllers are just regular JS classes with a state that can be modified in-place.

interface TodosState {
    todos: string[]
}

export class TodoListController extends Model<TodosState> {
    constructor() {
        super({ todos: [] });
    }

    getTodos(): string[] {
        return this.state.todos;
    }

    addTodo(text: string): void {
        this.state.todos.push(text);
    }

    editTodo(index: number, text: string): void {
        this.state.todos[index] = text;
    }
}

Use controllers in your views with useController:

export default function Home() {
  const todoController = useController(new TodoListController());
  // ...

Call methods on the controllers to update state:

return <div>
    <button onClick={() => todosController.addTodo("test")}/>
    <button onClick={() => todosController.editTodo(0, "test-edited")}/>
</div>

Render the state from a controller:

return <div>
    {todoController.state.todos.map((todo, i) => {
        return <div key={i}>{todo}</div>
    })}
</div>

Stateman controllers can be global singletons, meaning you can use their state in different places. That's pretty simple:

const userController$ = new UserController()

const Login = () => {
    const userController = useController(userController$)
    return <div>
        <button onClick={userController.login()}>
    </div>
}

const LoggedInView = () => {
    const userController = useController(userController$)
    return userController.state.getSession().username
}

They can also just be instantiated, meaning you can use the same controller logic for many instances of a component, e.g.:

const ReplyToComment = ({ commentId }: { commentId: number }) => {
    const postCommentController = useController(new PostCommentController(commentId))
    // ...
}

const Article = () => {
    const comments = ['a', 'b', 'c']
    return <div>
        {comments.map((comment, i) => {
            return <li key={i}>
                <span>{comment}</span>
                <ReplyToComment commentId={i}/>
            </li>
        })}
    </div>
}