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

ttls

v1.2.4

Published

Tagged template literals for various languages.

Readme

TTLs

Tagged Template Literals

A collection of TTLs for various syntaxes like CSS, HTML, and XML.

NOTE: The exports from this library do some minimal processing of the inputs to try to prevent things like XSS. The following functions are applied:

  • html: escaping (escape-html), sanitize (DOMPurify)
  • css: escaping (cssesc), validating (lightningcss)
  • xml: validating (fast-xml-parser)

These are mostly pretty tolerant, however they will throw an error if something is really incorrect.

The ttls-helpers package offers some helpful functions for common use cases like creating unique IDs, spreading an object into HTML attributes, generating css strings, etc.

There is also a companion VS Code extension, which offers syntax highlighting for the various formats either through a comment like /*{format}*/, e.g. `/*css*/`.hello { color: red }`, or through one of the TTL exports, like css`.hello { color: red }`.

If you don't want your input processed at all, you can either use the extension above with the comment-based format, or use the ttls-raw package. Under the hood, this package just uses the ttls-raw/curried export. Depending on your needs, you might look at using the curried function to create your own pipelines using things like prettier for formatting and html-validate for HTML validation, to make sure the output of the TTL is "correct" for your use case.

Examples

import { css, html, xml } from 'ttls';

html`<div>${ '< '}</div><img src=x onerror=alert(1)//>`; // => <div>&lt; </div><img src="x">
css`.${ '👍' } { color: red; }` // => .\\1F44D { color: red; }
css`.hello color: red; }` // => will throw