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

@apiuikit/web-component

v2.4.0

Published

Framework-agnostic web components for apiuikit — full-document and per-section (servers, operations, messages, schemas, info) custom elements for AsyncAPI and OpenAPI

Readme

@apiuikit/web-component

Framework-agnostic web components for apiuikit — use it from Vue, Angular, Svelte, plain HTML, or any environment that supports custom elements, with no React installation required on the consumer side.

Full-document elements:

| Element | When to use | |---|---| | <apiuikit-asyncapi-renderer> | You have a raw AsyncAPI YAML or JSON string | | <apiuikit-asyncapi> | You already have a parsed AsyncAPI document object | | <apiuikit-openapi-renderer> | You have a raw OpenAPI YAML or JSON string | | <apiuikit-openapi> | You already have a parsed OpenAPI document object |

Plus standalone elements for individual sections — <apiuikit-asyncapi-servers>, -operations, -messages, -info, their OpenAPI equivalents (<apiuikit-openapi-servers>, -endpoints, -webhooks, -info), and a single <apiuikit-schemas> shared by both spec types (components.schemas is the same shape either way) — for when you want just one part of a document rendered on its own.

Single-item elements (<apiuikit-asyncapi-operation>, <apiuikit-asyncapi-message>, <apiuikit-openapi-endpoint>, <apiuikit-openapi-webhook>, <apiuikit-schema>) go one step further and embed one item inline, picked by attribute: <apiuikit-openapi-endpoint operation-id="addPet">.

See docs/usage/with-webcomponents.md for the full prop reference.

If you're building a React app, use apiuikit directly instead of this package.

Install

npm install @apiuikit/web-component

Then load the elements and stylesheet once in your app:

import "@apiuikit/web-component";
import "@apiuikit/web-component/style.css";

No extra packages are required — React, ReactDOM, and parsing support are bundled in.

Modular imports

Only need one or two elements? Import just those instead of the full bundle:

import "@apiuikit/web-component/asyncapi-renderer";   // <apiuikit-asyncapi-renderer> only
import "@apiuikit/web-component/asyncapi";             // <apiuikit-asyncapi> only
import "@apiuikit/web-component/asyncapi-operations";  // <apiuikit-asyncapi-operations> only
import "@apiuikit/web-component/openapi-renderer";     // <apiuikit-openapi-renderer> only
import "@apiuikit/web-component/openapi";              // <apiuikit-openapi> only
import "@apiuikit/web-component/openapi-endpoints";    // <apiuikit-openapi-endpoints> only
import "@apiuikit/web-component/style.css";

(Every full-document and section element has a matching subpath — see the docs link above for the complete list.)

Quick start

<link rel="stylesheet" href="node_modules/@apiuikit/web-component/dist/web-component.css" />

<apiuikit-asyncapi-renderer id="doc"></apiuikit-asyncapi-renderer>

<script type="module" src="node_modules/@apiuikit/web-component/dist/web-component.es.js"></script>
<script type="module">
  const res = await fetch("./asyncapi.yaml");
  document.getElementById("doc").spec = await res.text();
</script>

CDN / no bundler

<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@apiuikit/web-component/dist/web-component.css" />
<script src="https://cdn.jsdelivr.net/npm/@apiuikit/web-component/dist/web-component.iife.js"></script>

<apiuikit-asyncapi-renderer id="doc"></apiuikit-asyncapi-renderer>
<script>
  document.getElementById("doc").spec = `asyncapi: 3.0.0
info:
  title: Demo
  version: 1.0.0`;
</script>

Full prop reference, framework integration notes (Vue, Angular, etc.), and configuration options are documented in docs/usage/with-webcomponents.md in the main repo.