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

@brixter/core

v0.1.0

Published

Agnostic brix render engine + format (parser, interpreter, YAML import/export)

Readme

@brixter/core

The agnostic brix engine that powers Brixter.

A pure parser + runtime interpreter for .brix markup, plus the brix document format (YAML import/export, field/definition types and helpers). It depends only on yaml and contains no editor, Svelte or DOM code, so a published site and the authoring dashboard can share the same render/format base.

Install

npm install @brixter/core

Entry points

| Import | Contents | |--------|----------| | @brixter/core | Everything: the document format (fields, definitions, builder helpers) plus the markup renderer. | | @brixter/core/render | Only the standalone renderer — parser + interpreter, no authoring helpers. Use this for build/SSR rendering to keep the bundle minimal. |

Rendering brix

import { renderBrixSource } from '@brixter/core/render';

const html = renderBrixSource(source, props);

Other renderer exports: render, renderToString, stripFrontmatter, parseTemplate (with the TemplateNode type).

Document format & helpers

The package root additionally exposes the brix document model and the helpers the authoring UI builds on — e.g. createBuilderDocument, createBlock, getCollectionItems, createBuilderDefaultsFromFields, and the Builder*/BrixYaml* types. These describe the .brix.yaml shape and drive schema inference; consumers rendering finished pages usually only need @brixter/core/render.

License

MIT