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

@jolly-pixel/asset-server

v5.0.0

Published

Back-end asset orchestration: event-sourced projection, reconciliation and catalog delivery

Readme

💃 Getting Started

Install the package with pnpm:

$ pnpm add @jolly-pixel/asset-server

👀 Usage example

import * as EventStore from "@jolly-pixel/event-store";
import { FilesystemAssetSource } from "@jolly-pixel/asset-source/node";
import { Server } from "@jolly-pixel/network";
import {
  createAssetBackend,
  textureAssetKind
} from "@jolly-pixel/asset-server";

using eventStore = await EventStore.persistence.sqlite(
  "./assets/.jollypixel/events.db"
);

await using backend = await createAssetBackend({
  source: new FilesystemAssetSource("./assets"),
  eventStore,
  handlers: [textureAssetKind()]
});

await using server = new Server();
backend.attach(server);

On startup, the backend catalogs files already present in ./assets. Changes made through backend.writer are appended to the event store and written to the asset source. Changes made by external tools are detected and appended as system events.

📚 API

  • Architecture: visual map of event flow, projections, live state and reconciliation
  • AssetBackend: setup, options and lifecycle
  • AssetWriter: create, update, rename and remove assets
  • Asset kinds: custom state, serialization and editing rooms
  • Catalog: catalog projection, network messages and HTTP access
  • Archive: ZIP export and import of an asset with its dependencies
  • Rooms: dynamic editing rooms and eviction
  • Sync: lifecycle events, snapshots and reconciliation

✨ Contributors guide

Read the contributing guide before submitting a change.

Run these commands from the monorepo root:

$ pnpm --filter @jolly-pixel/asset-server test
$ pnpm run lint

[!CAUTION] Include tests when adding a feature or fixing a bug.

📃 License

MIT