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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@beamformio/inbox

v0.1.1

Published

Drop-in notification inbox widget for SaaS applications

Downloads

8

Readme

Beamform Inbox

RelativeCI

Development

Prerequisites:

  • Install just - brew install just (macOS), cargo install just (Linux/Windows)
  • Uses pnpm for package management (inside Docker container)

Quick Start:

just up    # Start dev server
just open  # Open http://localhost:6006

Commands:

Uses Docker and justfile. Run just to see all commands.

| Task | Command | | ------------------- | ----------------------- | | Development | | | Start server | just up | | View logs | just logs | | Open Storybook | just open | | Stop server | just down | | Start Storybook | just storybook | | Testing | | | Lint | just lint | | Format | just format | | Unit tests | just test | | Test watch | just test-watch | | Building | | | Build components | just build-components | | Build widget | just build-widget | | Build both | just build-all | | Build Storybook | just build-storybook | | Analysis | | | Analyze components | just analyze | | Analyze widget | just analyze-widget | | Environment | | | Reset environment | just reset | | Update dependencies | just build |

Note: Do not run git or gh commands in the container.

Node.js Support

This package supports Node.js versions following our 2 LTS + Future LTS policy:

  • Two most recent LTS versions: Currently Node.js 20.x (Active LTS) and 22.x (Active LTS)
  • Current even releases that will become LTS: Currently 24.x (will become LTS in 2025)
  • Odd releases: Not supported (19.x, 21.x, 23.x) as they are short-lived and never become LTS
  • EOL or older LTS versions: Not supported after we add newer LTS support

Current support matrix: Node.js 20.x, 22.x, 24.x

We test against all supported versions in CI to ensure compatibility. The engines field in package.json reflects the minimum supported version.

Lifecycle

The project supports two distribution channels with different development workflows:

NPM Package (React Components) - Hot Reload ✅

  • Files: src/core/components/, src/core/primitives/, src/core/services/, src/stories/
  • Workflow: Make changes → Storybook updates automatically
  • No manual build required

CDN Distribution (Drop-in Widget) - Manual Build ❌

  • Files: src/packaging/widget.ts, src/widget/, CDN-related components
  • Workflow: Make changes → just build-widget → Refresh Storybook
  • Manual build required because CDN widget is built as IIFE bundle

When Manual Build is Required

# After changes to CDN widget files:
just build-widget
# Then refresh Storybook "Widget/CDN Drop-in Widget" story

File Change Impact

| File/Directory | NPM Hot Reload | CDN Manual Build | | ------------------------- | -------------- | ---------------- | | src/core/components/ | ✅ | ❌ Required | | src/packaging/widget.ts | N/A | ❌ Required | | src/widget/ | N/A | ❌ Required | | src/stories/ | ✅ | N/A |

Why CDN requires manual build: The drop-in widget is built as a self-contained IIFE bundle with React/SWR included, served as static files in Storybook. Hot reload can't watch/rebuild this automatically.