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

@burdenoff/fe-libs

v2026.919.1

Published

Burdenoff frontend primitives and domain libraries

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

burdenoffcorpburdenoffcorp

Keywords

Readme

@burdenoff/fe-libs

Frontend primitives and domain libraries for all Burdenoff products.

Architecture

This is a Layer 1 package - a monolithic package with subpath exports for all primitives.

Package Structure

@burdenoff/fe-libs/
├── /workflow    - Workflow primitives (Node, Canvas, Edge)
├── /tag         - Tag components
├── /form        - Form components
├── /button      - Button primitives
└── /shared      - Shared utilities (cn, types)

Usage

import { Button } from '@burdenoff/fe-libs/button';
import { WorkflowNode, WorkflowCanvas } from '@burdenoff/fe-libs/workflow';
import { cn } from '@burdenoff/fe-libs/shared';

Development

# Install dependencies
bun install

# Build library
bun run build

# Type check
bun run type:check

# Run all checks
bun run sanity

Components

Workflow Primitives

  • WorkflowNode - Renders a workflow node with status indicators
  • WorkflowCanvas - Canvas component for workflow builder with grid background

Button

  • Button - Versatile button component with variants (default, destructive, outline, secondary, ghost, link)

Shared

  • cn - Utility for merging Tailwind classes

shell-native (app shells only)

@burdenoff/fe-libs/shell-native is the shell-side native runtime: Capacitor (iOS/Android), Electron desktop and PWA wiring in one entry point. App shells import it; microfrontends never do — MFEs talk to the shell through window.__burdenoffNativeBridge (@burdenoff/fe-libs/shared/native).

Boot it once in main.tsx, before React mounts:

import { bootNativeShell, registerDeepLinkNavigator } from '@burdenoff/fe-libs/shell-native';

const shell = bootNativeShell({
  product: 'vibecontrols',
  appName: 'VibeControls',
  // Optional plugins are loaded ONLY through these loaders, so web-only shells
  // never bundle them.
  plugins: {
    updater: () => import('@capgo/capacitor-updater'),
    pushNotifications: () => import('@capacitor/push-notifications'),
  },
  push: { enabled: true, onToken: (token) => void registerDevice(token) },
  runtimeHooks: { syncPendingOperations: refetchAll, saveState: flushDrafts },
});

// Inside the router:
registerDeepLinkNavigator((path) => navigate(path));
// After the first meaningful paint:
void shell.markAppReady();

Boot order (each step is individually try/caught — boot never throws): preview → OTA notifyAppReady → auth-redirect intercept → external URL opener → native bridge + platform classes → device info → status-bar theme listener → keyboard → Android back button → deep links → network → app-state hooks → push listeners → splash safety timer (native) → PWA service worker (web) → desktop shell boot.

Contracts the shells and MFEs can rely on:

  • Window globals — __burdenoffNativeBridge, __burdenoffDeviceInfo, __burdenoffOpenExternal(url), __burdenoffPushToken, __burdenoffPwaInstallPrompt.
  • Body classes — platform-ios | platform-android | platform-web, platform-native, platform-preview, keyboard-open. <html> carries data-platform and (in preview) data-native-preview.
  • CSS var — --keyboard-height (0px when closed).
  • Window events — burdenoff:appReady, burdenoff:appStateChange, burdenoff:networkStatusChange, burdenoff:keyboardWillShow|DidShow|WillHide|DidHide, burdenoff:pushToken, burdenoff:pwaUpdateReady, burdenoff:pwaInstalled, burdenoff:pwaInstallAvailable. The shell listens for burdenoff:statusBarTheme.

Native preview flag

?__nativePreview=ios|android|pwa|desktop renders the installed-app chrome in a plain browser (persisted in sessionStorage, cleared with off). It is presentation only — real plugin calls stay gated on Capacitor.isPluginAvailable, and the flag is ignored inside a real native app.

Build-time config generators

defineCapacitorConfig(nativeConfig), defineWebManifest(nativeConfig) and renderServiceWorker(nativeConfig, version) are pure functions (no @capacitor/* imports) that emit each product's capacitor.config.ts, public/manifest.json and public/sw.js from its native.config.json (NativeConfig).

Tech Stack

  • React 19
  • TypeScript 5.9+
  • TailwindCSS v4
  • Radix UI (for accessible primitives)
  • Vite 7 (for building)