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

@amalgm/email-render

v0.1.2

Published

The portable email surface generated from Amalgm’s canonical rendering components.

Readme

Amalgm email rendering

The portable email surface of Amalgm UI. Notes and Chat use the canonical components directly; email imports their generated templates, glyphs and metrics and overrides only mail-client mechanics (tables, inline styles, PNG icons, and video preview cards). Channels imports this package. It does not own another renderer or visual token set.

Canonical sources: lib/rendering/, components/rendering/Citation.tsx, and components/rendering/icons/FileTypeIcon.tsx in the UI repository.

From the UI root, run npm run generate:email-render, then npm run check:email-render and npm run test:email-render. The drift check is required before packing or publishing. Never edit generated assets.

formatNotificationEmail(markdown, link, { appOrigin, sessionId }) renders HTML. prepareEmailIconAttachments(html, media, maximum) supplies referenced canonical icon PNGs; the caller owns attachment admission and persistence. Local media paths are data: this renderer never opens them or fetches a URL. mapMediaLines visits standalone media outside fenced code and shares the same reference parser with Channels' local file adapter. Soft line breaks inside an image label remain one reference; the parser and mediaReferenceMarkdown normalize them to spaces without changing its source.

Delivery

The Email renderer package workflow packs once and examines that same archive on Linux, macOS, and Windows. scripts/email-render/package.mjs publish accepts only a main-source archive with all three matching proofs and uses the existing npm account. Set AMALGM_EMAIL_RENDER_ARTIFACT to the downloaded artifact folder. Bump this workspace package's version and its root workspace dependency together when publishing changed bytes. Consumers pin that exact version.