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

@bimetal/sync

v0.37.0

Published

Sync primitives (v0.15). Framework-agnostic SyncTransport interface + InMemorySync loopback. Server-authority model, optimistic locking, no resolvers, no previous, no LWW.

Readme

@bimetal/sync

Sync-Primitive (v0.15) für BIMETAL. Ein strukturelles, framework-agnostisches SyncTransport-Interface plus eine In-Memory-Loopback-Implementierung — die Grundlage für Multi-Client-Synchronisation über eine Server-Autorität.

Das Modell ist bewusst schlank: Server-Autorität, Optimistic Locking, First-Writer-Wins. Keine Resolver, kein previous-Feld, kein Last-Write-Wins, keine Timestamp-Tiebreaker, keine Merges im Kern — ein Konflikt wird laut (ConcurrencyError), nicht still aufgelöst. Fachliche Merge-/Recovery-Strategien gehören in die App, nicht ins Framework.

Installation

npm install @bimetal/sync @bimetal/event-sourcing

Was das Paket liefert

| Export | Zweck | |--------|-------| | SyncTransport | Das strukturelle Transport-Interface (senden/empfangen von Sync-Nachrichten) — ein WebSocket-Adapter (@bimetal/sync-ws) implementiert es. | | createSyncedEventStore(options) | Composer (kein Replacement): wickelt einen lokalen EventStore in einen sync-fähigen Store — lokale Appends gehen über den Transport an die Autorität, Remote-Events werden eingefoldet. Konfiguration über ein SyncedEventStoreOptions-Objekt. | | createInMemorySync() / createInMemorySyncAuthority() | Loopback-Transport + In-Memory-Autorität — für Tests und Single-Prozess-Szenarien. | | InMemorySyncAuthority | Der Autoritäts-Typ. |

Architektur

Cross-cutting (Transport). Konzepte: Event-Sourcing-Konzept und Backend-Überblick — dort auch „Wie groß wird das?“, die Grenze des Log-im-Client (Optimistic Locking / Concurrency).