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

@tasfer/code

v0.1.4

Published

Syntax-highlighted code block node for @tasfer/editor (opt-in; owns the highlight.js grammar set).

Readme

@tasfer/code

The opt-in syntax-highlighted code block for @tasfer/editor — on-canvas layout, editing behavior, and highlighting.

Code splits differently from math: the type is core, the painter is not. @tasfer/editor tokenizes fenced code blocks, describes the CRDT shape, and owns the Markdown/HTML/text round-trip, so a document containing code parses, syncs, serializes, and exports with baseSchema alone. What lives out here is the painter — because the highlighting carries a grammar set far larger than the engine itself.

Install

npm install @tasfer/editor @tasfer/code

Usage

import { baseSchema, createEditor } from "@tasfer/editor";
import { codeExtension } from "@tasfer/code";

const schema = baseSchema.use(codeExtension());

const editor = createEditor({
  element,
  schema,
  markdown: "```ts\nconst x = 1\n```",
});

Skip the package and nothing is lost from the document: the block still round-trips and still replicates, it simply has no painter and renders as the placeholder any unregistered block type gets.

Also exported

  • CODE_LANGUAGES, codeLanguageLabel — for a language picker.
  • INDENT_CODE, OUTDENT_CODE — actions to wire into a toolbar or shortcut.
  • highlightLine — the tokenizer on its own, if you want it elsewhere.
  • CodeNode — the node class, subclassable.

Highlighting is powered by lowlight (highlight.js).

Documentation

tasfer.app/docs/editor/api-schema#code

License

MIT