asset-cache is a indexeddb persistence layer for caching large assets. It provides a simple interface to fetch() remote assets which are automatically persisted for subsequent requests.

A Metalsmith plugin to cache build results for subsequent runs

A generic context menu

Grunt task to enable debugging for subsequent tasks.

Response Pool is a very small library, based on js-csp, that can be used to pause subsequent function calls and pass a value from the first call in the concurrent group to the callback functions of subsequent calls as soon as it becomes available.

Clones Node starter projects from Git and initializes for subsequent modification

A backend system developed based on Express, including login, token verification, form curl, etc., in subsequent iterations

A Tailwind that lets you target subsequent-sibling or "next" element

Simple graphical authorization with login and password input and subsequent issuance of JWToken for express with fine tuning

Everyday 30 million people experience. It's reliable, flexible and extendable carousel.

The markup for subsequent integration with CMS. Contains raw HTML files and other resources.

Ensure a function is called only once, returning the cached result on subsequent calls. Useful for initialization functions or expensive operations that should run exactly once.

An [Insomnia](https://insomnia.rest/) plugin to save a access token from a login/auth request to be used in subsequent request through a template variable.

Runs typescript type checker and linter on separate process.

Prompts user for a string value once, caches it in a file, returns that value for every subsequent invocation

The `AssetServerPlugin` serves assets (images and other files) from the local file system. It can also perform on-the-fly image transformations and caches the results for subsequent calls.

Works just like a normal memoize function. The only difference is that it expects the function you are memoizing to return a promise. Until that promise has resolved/rejected, subsequent calls to the function will return the same promise.

<h1 align=center>Unfeed</h1> <p align=center>A fork of <a href="https://github.com/rowyio/feedbackfin">Feedback Fin</a> with more customization. Refer to <a href="https://github.com/wzulfikar/unfeed/pull/1">PR #1</a> (and subsequent PRs) to see what chang

when you want to fire an event no matter how a process exits.

Canonical journal-entry types and balance utilities shared across FlowState finance consumers. Phase 1 ships types + calculations; the posting engine, mapping resolver, and orchestrator land in subsequent phases (see docs/specs/2026-05-02-flowstate-financ