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

@bkper/web-components

v0.2.0

Published

Framework-agnostic web components and browser helpers for Bkper apps

Readme

@bkper/web-components

Framework-agnostic browser helpers and future web components for Bkper apps.

npm

Installation

Install this package when you want to use bundled helpers:

bun add @bkper/web-components
npm i -S @bkper/web-components

For first-paint theme initialization, apps can load the CDN script directly without installing the package.

Theme init script

Use the blocking classic script before loading app modules to avoid a wrong-theme first paint:

<script
    src="https://cdn.jsdelivr.net/npm/@bkper/[email protected]/dist/theme-init.global.js"
    crossorigin="anonymous"
></script>

The global script is intentionally small and self-contained. It reads the persisted Bkper theme, applies the resolved theme to <html>, and listens for theme messages from a parent/opener Bkper shell.

This is the recommended default for embedded Bkper apps.

Bundled theme helpers

Use @bkper/web-components/theme when bundled client code needs access to the same theme rules:

import {
    applyTheme,
    createThemeChangeMessage,
    getTheme,
    isDarkTheme,
    setTheme,
} from '@bkper/web-components/theme';

applyTheme(getTheme());
setTheme('dark');
applyTheme('dark');

const dark = isDarkTheme();
iframeWindow.postMessage(createThemeChangeMessage('dark'), targetOrigin);

The bundled helpers centralize theme constants, persistence, migration, message shape, theme resolution, and DOM application. App shells still own rendering, event-bus integration, and component placement.

Do not import a bundled auto-initializer when the global init script is already present. Use explicit helpers from @bkper/web-components/theme instead.

Visible custom elements may be added in future releases when there is a concrete shared UI use case.

Browser compatibility

This package targets modern browsers with classList, cookies, and matchMedia support. The root theme helper entrypoint can be imported by SSR/build tooling. The global theme init script is a classic script intended to run in a browser <head> before app modules.

License

Apache-2.0