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

@edoc-space/plugin-openapi

v1.0.0

Published

OpenAPI reference component for E-Doc MDX pages.

Readme

@edoc-space/plugin-openapi

English | Русский

OpenAPI reference component for E-Doc MDX pages.

Use it when a documentation page needs to render an OpenAPI JSON specification without writing the endpoint list by hand.

Installation

Install the plugin into the E-Doc local plugin overlay, not into the core application package:

cd local/plugins
yarn add @edoc-space/plugin-openapi

Or with npm:

cd local/plugins
npm install @edoc-space/plugin-openapi

Usage

Put the specification into local/storage/edoc/static, for example:

local/storage/edoc/static/openapi.json

Then import the component from an .mdx page:

import { OpenApi } from '@edoc-space/plugin-openapi'

<OpenApi source="/storage/edoc/static/openapi.json" />

The package imports its CSS from the entrypoint. E-Doc resolves the package from local/plugins/node_modules.

You can also pass operations directly:

<OpenApi
  title="Project API"
  operations={[
    {
      method: 'get',
      path: '/users',
      summary: 'List users',
      tags: ['Users'],
      responses: {
        '200': { description: 'User list' },
      },
    },
  ]}
/>

Props

type OpenApiProps = {
  title?: string;
  source?: string;
  operations?: OpenApiOperation[];
  groupBy?: 'tag' | 'none';
  showSearch?: boolean;
  defaultExpanded?: boolean;
};

Local Development

This repository uses the same package shape as the published npm package:

yarn install
yarn typecheck
yarn build
npm pack --dry-run

Before publishing, make sure the dry-run output contains only dist, README.md, README_RU.md, LICENSE, and package metadata.