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

@earlytexts/markit

v3.2.2

Published

Markit is a lightweight textual markup language similar to Markdown, but designed for use in textual preservation projects, as a more human-readable alternative to TEI XML. It compiles to JSON for representing document structure and metadata, while the te

Readme

Markit

Markit is a textual markup language similar to Markdown, but designed for use in textual preservation projects, as a more human-readable alternative to TEI XML. It compiles to JSON for representing document structure and metadata, while the text content itself can then be further compiled to either plain text or HTML.

Markit comes with a VS Code extension which supports syntax highlighting, block folding, in-editor error reporting, and a live preview of the rendered HTML output.

How to Use

  1. Install Microsoft's VS Code editor.
  2. Install the vscode-markit extension.
  3. Write your Markit document in a .mit file, following the syntax specified in the specification.
  4. Preview the rendered HTML output using the live preview feature (Cmd+Shift+V or Ctrl+Shift+V).
  5. Compile your Markit document to JSON, HTML, or plain text using the provided commands (Cmd+Shift+P or Ctrl+Shift+P to open the command palette, then search for "Markit: Compile to JSON/HTML/Text").

Markit Syntax

  • See the specification for a complete description of the Markit syntax.
  • See the example.mit file for a sample Markit document demonstrating all the features.

Programmatic Use (Advanced)

The Markit compiler is written in TypeScript and can be used programmatically in your own projects. You can install it via npm:

npm install @earlytexts/markit

Then you can import the compiler functions in your code:

import { compile, renderHTML, renderText } from "@earlytexts/markit";

const markitInput = `...`; // your Markit document as a string
const [document, errors] = compile(markitInput);
const htmlOutput = renderHTML(document);
const textOutput = renderText(document);

The compile function returns a tuple of the form [document, errors], where document is the compiled result and errors is an array of any syntax errors encountered during compilation. The document is always produced even if there are errors, so you can choose to use it anyway (e.g. for a best-effort preview), but you should always check the errors array to see if there were any issues with the input.

The two functions renderHTML and renderText take a compiled document and return a string - either an HTML representation of the document or plain text.