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

@drb0r1s/engineer

v1.0.1

Published

Lightweight and fast state manager built for high-frequency UI updates.

Readme

Engineer

A minimal, dependency-free state manager for JavaScript applications that need fast, predictable state updates without the overhead of larger state libraries.

Why Engineer?

Engineer was built while developing Assembly Reality, a web-based assembly language simulator (my Bachelor's thesis project at UP FAMNIT). The UI needs to reflect rapid, frequent state changes: CPU registers, memory, and I/O devices updating in near real time as code executes. Redux (and other general solutions) were too slow for this use case, the overhead of its dispatch and selector model introduced noticeable lag under frequent updates.

Engineer solves this with a much smaller surface area: a plain key/value store with direct subscriptions and an explicit batching mechanism, so consumers only get notified when they actually need to be.

Features

  • Simple get/set/delete key-value API.
  • Direct event subscriptions per key, no selectors or reducers.
  • sequence() batching: group multiple updates together and fire listeners only once all of them are applied.
  • No dependencies, no build step required to use.

Installation

npm i @drb0r1s/engineer
import { Engineer } from "engineer";

Usage

const engineer = new Engineer({
    theme: "dark",
    isRunning: false
});

// Subscribe to changes
const unsubscribe = engineer.subscribe("isRunning", value => {
    console.log("isRunning changed to", value);
});

// Update a value
engineer.set("isRunning", true);

// Batch multiple updates, listeners fire once per key after the sequence completes
engineer.sequence(() => {
    engineer.set("isRunning", false);
    engineer.set("theme", "light");
});

// Custom events not tied to a stored value
engineer.trigger("reset", { reason: "user requested" });

// Clean up
unsubscribe();

API

new Engineer(initialValues = {})

Creates a new instance seeded with the given key-value pairs.

.get(key)

Returns the current value for key.

.set(key, value)

Updates the value for key and notifies subscribers, unless called inside a sequence().

.delete(key)

Removes key from the store.

.subscribe(event, callback)

Registers callback to run whenever event (a key or a custom trigger name) fires. Returns an unsubscribe function.

.trigger(event, data)

Manually fires listeners for event with data, without touching the store.

.sequence(callback)

Runs callback synchronously, deferring all set/trigger notifications until it finishes, then fires each affected listener once with its final value. Useful for avoiding redundant re-renders when updating several related values at once.

Used by

Assembly Reality's entire UI state layer (theme, editor state, CPU/memory view toggles, execution state, autosave flags) is built directly on top of Engineer.