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

@psspl-emp/support-widget

v1.0.0

Published

Reusable React customer-support chat widget

Readme

@nexora/support-widget

Reusable React support chat for any host integrated with the AI Support Service. The package has no merchant auth, router, store, commerce route, tenant credential, or API-key dependency.

Open the complete developer and API documentation.

Quick start

import { AISupportProvider, useAISupport } from '@nexora/support-widget'
import '@nexora/support-widget/styles.css'

// 1 — Implement getSessionToken in your application. Your host decides how to
//     obtain the token. The widget never receives an app token or tenant API key.
async function getSessionToken({ orderId, orderItemId }) {
  return myHostIntegration.createSupportSession({ orderId, orderItemId })
}

// 2 — Wrap your app once near the root.
function Root() {
  return (
    <AISupportProvider
      apiBaseUrl="https://ai-support.example.com"
      getSessionToken={getSessionToken}
      onChooseAnotherOrder={() => navigate('/orders')}
    >
      <App />
    </AISupportProvider>
  )
}

// 3 — Open general or order support from any descendant component.
function GeneralHelpButton() {
  const { openSupport } = useAISupport()
  return <button onClick={() => openSupport()}>Need help?</button>
}

function OrderHelpButton({ orderId, orderItemId }) {
  const { openSupport } = useAISupport()
  return (
    <button onClick={() => openSupport({ orderId, orderItemId })}>
      Get help with this order
    </button>
  )
}

Authentication lifecycle

openSupport({ orderId, orderItemId })
  │
  ▼
getSessionToken({ orderId, orderItemId })     ← host-defined integration
  │  merchant authentication stays outside the package
  │  ← { sessionToken, expiresIn }
  │
  ▼
Widget stores sessionToken in memory only     ← never localStorage / sessionStorage
  │
  ▼
All chat API calls: Authorization: Bearer <sessionToken>
  │
  ├── 401 SUPPORT_SESSION_EXPIRED?
  │     │
  │     ▼
  │   getSessionToken() called again (shared lock — one refresh for N concurrent requests)
  │     │  success → update in-memory token, retry original request once
  │     │  failure → show session error, stop retrying
  │     ▼
  └── continue

Provider props

| Prop | Required | Default | Description | |---|---|---|---| | apiBaseUrl | Yes | — | AI Support Service REST and Socket.IO base URL | | getSessionToken | Yes | — | async ({ orderId, orderItemId }) => string — acquires a support session JWT | | onChooseAnotherOrder | No | — | Callback when the user picks a different order | | showLauncher | No | true | Show the floating "Need help?" button | | supportMountSelector | No | [data-ai-support-root] | CSS selector for page-mode portal |

useAISupport() return value

| Member | Type | Description | |---|---|---| | openSupport | async (ctx?) => void | Acquires session token and opens the widget | | closeSupport | () => void | Hides the widget UI (does not end the backend conversation) | | sessionAcquireError | string \| null | Set when token acquisition or refresh fails |

What is NOT in scope

  • No merchant API key or tenant ID is accepted by the widget
  • No plain HTML / CDN bundle
  • No host access token transmitted to chat APIs
  • No customerId prop (server derives identity from the session token)