Bayon AI logo
BAYON AI

NPM packages for Bayon AI products

Build products on shared packages for APIs, design, analytics, authentication, notifications, email, MCP, gamification, offline storage, document editing, and agent contracts—without copying infrastructure between apps.

Browse NPM packagesOpen text editor docs

Choose an NPM package

Find the reusable layer your product needs, then review its installation, usage, integration contract, and host-owned boundaries before adopting it.

NPM Packages

Choose a package to review its purpose, installation, usage, integration contract, and boundaries. Dedicated documentation appears when available.

Published
v0.5.0

@bayonai/sdk

TypeScript SDK for the BayonAI Firebase API and product integrations.

NPM
Published
v2.0.4

@bayonai/rich-text-editor

Reusable rich-text document utilities, native React editing components, and unsaved-change session controls.

DocsNPM
Published
v0.15.0

@bayonai/offline

Reusable offline read-cache and pending-write primitives for Bayon AI apps.

NPM
Published
v0.1.4

@bayonai/analytics

Shared Bayon AI analytics and Next.js log-export adapter with PostHog provider support.

NPM
Published
v0.5.0

@bayonai/firebase-auth

Reusable Firebase authentication actions, React provider, MUI login surfaces, and server-owned email Functions.

NPM
Published
v0.2.1

@bayonai/push-notifications

Provider-neutral notification contracts with Capacitor Firebase, local notification, and Firebase Admin adapters.

NPM
Published
v0.2.0

@bayonai/transactional-email

Provider-neutral transactional email delivery with branded, overridable HTML and text templates.

NPM
Published
v0.2.0

@bayonai/transactional-email-firebase

Firebase Functions, Firestore mail operations, and an MUI admin surface for transactional email.

NPM
Published
v1.0.14

@bayonai/mcp

Shared OAuth, PKCE, bearer-challenge, and secret helpers for remote Model Context Protocol servers.

NPM
Published
v0.1.1

@bayonai/gamify

Storage-agnostic progress, goal, rank, and contextual-guidance primitives for Bayon AI applications.

NPM
Published
v1.2.0

@bayonai/ui

Styling-independent React primitives for actions, feedback, navigation, and interaction.

DocsNPM
Internal
v0.1.0

@bayonai/website-agent

Shared public and internal Bayon AI agent contracts for website chat and operator workflows.

Published
v1.4.0

@bayonai/mui-design

Shared Bayon AI Material UI theme, tokens, page recipes, and reusable React surfaces.

NPM

@bayonai/ui

Styling-independent React primitives for actions, feedback, navigation, and interaction.

Open docsNPM

Use this package when a React app needs reusable interaction primitives while retaining its own styling, data access, authorization, and request lifecycle.

  • Loading buttons, sticky form actions, and dialog controls
  • Status notices, loading indicators, toasts, and swipe rows
  • Link previews, lightbox, layout, and scroll primitives
  • Typed ESM and CommonJS subpaths for explicit, tree-shakeable imports

Package

@bayonai/ui

Current version: v1.2.0

Source: npm:@bayonai/ui

Boundaries

  • Does not own authentication, authorization, persistence, or routing.
  • Does not start uploads, retries, transactions, or analytics transport.
  • Does not choose product-specific copy, confirmation policy, or request lifetimes.
  • Does not replace native touch and keyboard verification in the consuming application.

Install

npm install @bayonai/ui

Verification or workspace command:

npm view @bayonai/ui version

Usage

import { StatusNotice } from '@bayonai/ui/feedback';

<StatusNotice tone="success" message="Changes saved." />;

Integration checklist

  1. Install the package and satisfy its published React and React DOM peer dependencies.
  2. Import only the documented component-family subpaths; no root entrypoint is published.
  3. Style the primitives with host CSS or native styles and pass application-owned state and callbacks.
  4. Verify keyboard access, focus, disabled states, and responsive behavior in the consuming app.

Public contract

Consume the selected package contract directly instead of copying configuration into app components.

Import the published actions, feedback, layout, lightbox, links, scroll, sections, swipe, or toasts subpath

Consumers provide the declared React and React DOM peers; styling belongs to the host

Host applications own content, permissions, data access, and action callbacks

Feedback and interaction surfaces preserve host-owned request and recovery state

Building a Bayon AI app surface?

Start with the shared package boundary that matches the product surface, then keep app-specific routing, auth policy, storage, and user-facing workflows in the consuming app.

Talk to Bayon AI