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

@compoundlabs/tearline

v0.2.0

Published

Wrap any HTML in one tag and it prints out as a thermal receipt. Save it as a PNG. Zero dependencies, no build step.

Readme

Tearline

Any HTML you wrap in this one tag prints out as a thermal receipt. Then save it as a PNG.

Zero dependencies. No build step. Works from a <script> tag. MIT.

npm i @compoundlabs/tearline
import '@compoundlabs/tearline';

Or with no bundler at all:

<script type="module" src="https://tearline.thecompound.tech/tearline.js"></script>

<tear-line barcode="047320260726">
  <h1>MERIDIAN</h1>
  <small>Coffee &amp; Provisions</small>
  <hr>
  <p>Cortado · 4.25</p>
  <p><strong>Total · 4.25</strong></p>
</tear-line>

Attributes

| | | |---|---| | width | paper width in px (default 330) | | seed | integer; same seed gives the same tear and barcode (default 1) | | barcode | string to render as bars; omit for none | | tilt | degrees of rotation (default -1.15) | | flat | present means no rotation and no drop shadow, for embedding and export | | animate | present means a print-out reveal on first paint |

Methods

await el.toBlob({ scale: 2 });     // Blob
await el.toDataURL({ scale: 2 });  // string
await el.download('receipt.png');  // saves it

The export event

tearline:stage fires as an export moves through its four real steps: flatten, serialise, rasterise, encode. rasterise is where the time and the failures both live.

The one constraint

Rendering to an image uses an SVG <foreignObject>, which cannot reach across the network. Any <img> inside the receipt must be a data: URI or the export will drop it. Text and CSS are inlined automatically.

Naming

Published under the studio's original scope because the registry refuses the bare name tearline: its similarity filter reads it as too close to readline. The element is <tear-line> either way. The studio is Compound Labs at thecompound.tech; the @compound scope on npm belongs to another account, so the package keeps the scope it was first published under.

Live playground: https://tearline.thecompound.tech