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

@basemark/core

v0.1.1

Published

Markdown + directive parser and component registry — framework-agnostic

Readme

@basemark/core

The engine behind Basemark: parses Markdown with directive syntax (::name{attrs}), resolves each directive against a component registry, validates its props, and renders the result — either to real DOM elements or to a plain HTML string. Framework-agnostic and dependency-light; domain component packages (@basemark/bio, @basemark/common, @basemark/charts) build on top of it.

Install

bun add @basemark/core

Usage

import { createRegistry, renderMarkdown } from '@basemark/core';

const registry = createRegistry();
registry.register('my-widget', {
	tag: 'my-widget-element',
	domain: 'demo',
	title: 'My Widget',
	description: 'A custom element registered directly, without a domain package.',
	schema: { label: { type: 'string', required: true } },
});

renderMarkdown('::my-widget{label="Hello"}', registry); // → a DocumentFragment with <my-widget-element label="Hello">

For a static HTML string instead of live DOM (e.g. server-side), use renderMarkdownToHtml().

A bad directive (unknown name, invalid prop, unclosed container) never disappears silently — it renders a visible error element in place, with any swallowed content still shown inside it.

Theming

theme.css ships shadcn-compatible CSS custom properties (--background, --primary, --radius, --font-sans, ...) on :root/.dark, plus base styling that reads them. Every component (this package, bio, common, charts) reads the same tokens inside its own shadow root — retheming is plain CSS, no JS API.

  • Already have a shadcn theme? Don't import theme.css — define the same token names on your own :root/.dark; custom properties inherit through Shadow DOM for free.
  • Want our defaults, tweaked? Import theme.css, then redefine just the tokens you want on :root/.dark — last one in the cascade wins, live, no rebuild.
@import '@basemark/core/theme.css';

:root {
	--primary: oklch(0.55 0.2 260);
	--radius: 0.5rem;
	--font-sans: 'Inter', sans-serif;
}

theme.css's own default values are a starting palette, not a fixed brand — override anything you don't like.