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

@coreui/astro-docs

v0.1.0-beta.14

Published

Shared Astro docs engine for CoreUI libraries (free + pro, all frameworks).

Readme

@coreui/astro-docs

Shared Astro docs engine that powers the documentation sites for the CoreUI component libraries — free and Pro, across every framework (vanilla JS, React, Vue, Angular). It ships the layout, navigation, search, MDX shortcodes (Example, Callout, Api, …) and the build-time integration that renders runnable examples straight from your library source.

Installation

npm install @coreui/astro-docs

Requires Astro ^6.4 (declared as a peer dependency). The consumer project also needs the matching base library, which the engine reads the SCSS source from:

  • free editions → @coreui/coreui
  • Pro editions → @coreui/coreui-pro

Usage

Add the integration to astro.config.mjs. Place coreuiDocs() before @astrojs/mdx, and spread it (it returns an array of integrations):

import { defineConfig } from 'astro/config'
import mdx from '@astrojs/mdx'
import { coreuiDocs } from '@coreui/astro-docs/integration'

export default defineConfig({
  integrations: [...coreuiDocs(), mdx()],
})

For React or Vue docs, add that framework's renderer too (@astrojs/react / @astrojs/vue) so example islands hydrate.

coreuiDocs() also handles the Vite side of the docs chrome for you (it pre-bundles the sandbox client's lz-string / @stackblitz/sdk deps in dev), so wiring it directly — as every CoreUI docs project does — is the supported path.

Edition detection

The engine auto-detects the edition from the consumer's dependencies: if @coreui/coreui-pro is present it builds the Pro docs, otherwise the free ones. The base SCSS is resolved from node_modules/@coreui/<edition> (or a sibling <edition>/ source directory in a monorepo).

Options

coreuiDocs({
  data: 'src/data',          // sidebar.yml, config.yml, logo.svg
  sandbox: 'src/sandbox.ts',  // per-framework StackBlitz `buildProject`
  config: undefined,          // path to the library config.yml ([[config:…]])
})

The publish URL is config-driven: coreuiDocs() reads seo.url from <data>/config.yml and derives Astro's site + base from it.

MDX components

These are auto-imported into every .mdx page (no import needed): Example, Code, Callout, AddedIn, ScssDocs, JSXDocs, Api.

Injected routes & AI artefacts

coreuiDocs() prerenders a set of routes on every docs site, for readers and for LLM / AI agents:

  • llms.txt — an llmstxt.org index of every page.
  • llms-full.txt — the whole documentation as a single Markdown file.
  • <slug>.md — a clean Markdown view of each page (linked from the page chrome).
  • api.json — every component's generated API (props / events / slots), keyed by component name, from src/api/*.api.json (see @coreui/astro-docs-api-generator).
  • a 404 page, sitemap.xml and robots.txt.

A build-time broken-link check runs over the internal links and fails the build on any broken link.

License

MIT © CoreUI