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

@dialstack/sdk-js

v3.5.0

Published

DialStack browser SDK — initialisation, REST client and the self-registering web components

Readme

@dialstack/sdk-js

The DialStack browser SDK — initialization, the REST client, and six self-registering web components.

Everything a plain HTML or JavaScript page needs. React bindings live in @dialstack/sdk-react, which peers on this package.

Install

npm install @dialstack/sdk-js

Or from a <script> tag, no bundler required:

<script src="https://unpkg.com/@dialstack/sdk-js"></script>

The script build exposes everything on window.DialStack.

Usage

import { loadDialstackAndInitialize } from '@dialstack/sdk-js';

const dialstack = await loadDialstackAndInitialize({
  publishableKey: 'pk_live_…',
  fetchClientSecret: async () => {
    const res = await fetch('/api/dialstack-session', { method: 'POST' });
    return (await res.json()).client_secret;
  },
});
<dialstack-call-logs></dialstack-call-logs> <dialstack-voicemails></dialstack-voicemails>

Importing this package registers the elements

That is a side effect, and it is deliberate: the entry point imports each component module, and each ends in customElements.define(...). So a single import '@dialstack/sdk-js' is what makes <dialstack-call-logs> a real element rather than an inert unknown one.

Two things follow.

sideEffects is an allowlist, not false. A blanket false would let a bundler drop those imports as unused, and the failure is silent — document.createElement succeeds for an unregistered tag and returns an element that renders nothing, with no error. If you are vendoring or re-bundling this package, preserve that field.

Use ./pure when you do not want the side effect. Same surface, nothing registered on import; you call registerComponents() yourself. That is what you want for server-side rendering, for tests, and anywhere a module-level customElements.define would run too early or in the wrong realm.

import { registerComponents, loadDialstackAndInitialize } from '@dialstack/sdk-js/pure';

if (typeof window !== 'undefined') registerComponents();

Errors

Catch API failures with isApiError, not instanceof ApiError:

import { isApiError } from '@dialstack/sdk-js';

try {
  await dialstack.phoneNumbers.list();
} catch (err) {
  if (isApiError(err) && err.status === 409) {
    /* … */
  }
}

instanceof compares against one specific class object, so it returns false whenever two copies of this package end up in a tree, or when the error crosses a realm. isApiError reads the fields carried on the error itself and cannot skew.

Which package do I want?

| You are building | Install | | ----------------------------- | ------------------------------------- | | A plain HTML page | this package alone | | A React app with DialStack UI | this package + @dialstack/sdk-react | | A softphone in any framework | @dialstack/sdk-webrtc | | A Node backend | @dialstack/sdk-server |

Documentation

Full documentation: https://docs.dialstack.ai/sdks

License

MIT