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

@bandeira-tech/b3nd-web

v0.5.1

Published

Browser-focused B3nd SDK bundle

Readme

b3nd/sdk provides client/server application protocol with multiple backend support and batteries included

b3nd/sdk is intended to support the design of allowing applications to manage their data schemas on their clientside frontends and use a secure and scalable backend solution that is flexible both ways both for the client app and the backend provider

b3nd/sdk is used in applications that are nodes to a network that may be local and made of 1 and can run even on your browser using local storage or indexeddb or in memory even, same for a script, or can connect to an http api that runs a simple deno kv or sqlite backend, or connects with multiple other nodes via websocket and http to broadcast and distribute persistence

Target Module Components Topology

b3nd/sdk

  • backends/{memory,http,websocket,localStorage,denokv,postgres,...}
  • client
  • types

b3nd/sdk/backends export unified interfaces for different backends, they require initialization with shared standards like backend schema that maps program urls (protocol://toplevel) to validation functions, and also take custom configuration related to the actual backend, i.e. connection string for postgres, url for websocket and http and so on

b3nd/sdk/client exports unified interface to route message for multiple backends, it's initialized with a client schema that maps programs urls (protocol://toplevel) to target backend instance programs

So while backend schema defines what programs are supported and available in a backend instance, the client schema defines what programs are routed to what backends

This way browser apps can communicate with multiple http and websocket backends, as well as have a local instance; also http apis and websocket servers can be setup in meshes to work together for HA or other distributed designs

Development

b3nd/sdk must

  • ALWAYS have a test for each component to automate validation and simplify troubleshooting
  • NEVER catch/hide/garble errors
  • ALWAYS leave it to the user to decide how to best handle errors for their applications