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

@trevixal/extension-blocks

v1.0.5

Published

Structural blocks for the Trevixal editor: callouts, toggles, columns, cards, timelines, page breaks, badges, buttons, footnotes and anchors.

Downloads

519

Readme

@trevixal/extension-blocks

CI npm types license

Documentation · Live editor · Changelog · Issues

The Trevixal editor

Features

  • Callouts, toggles, columns, cards and timelines
  • Page breaks, badges, buttons, footnotes and anchors
  • 6.8 kB minified and gzipped, with TypeScript types in the package

The structural blocks a document needs beyond paragraphs and lists: callouts, toggles, columns, cards, timelines, tabs, accordions, footnotes and citations.

npm install @trevixal/extension-blocks

Usage

Merge the nodes into your schema:

new Schema({ nodes: { ...defaultNodes(), ...blockNodes() }, marks: defaultMarks() })
import { blockKeymap, blockBindings, insertCallout, insertColumns } from '@trevixal/extension-blocks'

const editor = createEditor({ schema, element, keymap: blockKeymap() })
blockBindings(editor) // click handling for toggles, tabs and accordions

editor.exec(insertCallout('warning'))
editor.exec(insertColumns(3))

The blocks

| Block | Commands | | --- | --- | | Callout, five tones | insertCallout(variant), setCalloutVariant | | Toggle | insertToggleBlock, toggleToggleOpen | | Columns, 2-4 | insertColumns(count), setColumnCount | | Card, timeline | insertCard, insertTimeline, insertTimelineItem | | Tabs | insertTabs(count), addTab, removeTab, moveTab, activateTab | | Accordion | insertAccordion, addAccordionItem, setAccordionItemOpen, toggleAccordionExclusive | | Badge, button, anchor | insertBadge, insertButton, insertAnchor | | Footnotes, citations | insertFootnote, insertCitation, insertReferenceList, renumberCitations | | Page break | insertPageBreak |

Getting out of a container

blockKeymap() supplies the two gestures every nested block needs. Enter on an empty trailing paragraph inside a container leaves it, without that, a callout at the end of the document traps the cursor, because every Enter makes another paragraph inside it. Enter on a toggle summary, tab title or accordion title moves into the body rather than splitting the title.

Tabs and accordions in an export

An accordion is a native <details>, so it keeps working in a saved file because the browser owns it. A tab strip is laid out from a data-active attribute that only the editor moves, so @trevixal/ui inlines a small script into exports to make the titles work there too. Before adding an interactive block, decide what it does in an export, and add the print rule, or the PDF quietly loses whatever is not on top.

License

Apache-2.0