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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@trunkjs/prolit

v1.0.17

Published

Prolit generates lit-html template from easy to use heml templates.

Downloads

42

Readme

@trunkjs/prolit

Prolit lets you write concise, HTML-like templates that compile to efficient lit-html templates.

Why Prolit?

  • HTML-like templates with simple control flow and interpolation.
  • Structural directives: *if, *for, plus helpers *do, *log.
  • Bindings: @event, .prop, ?attr, ~class, ~style.
  • Works with LitElement and lit-html 3.x.

Quick, all-in-one example

import { LitElement } from 'lit';
import { customElement } from 'lit/decorators.js';
import { scopeDefine, prolit_html } from '@trunkjs/prolit';

const scope = scopeDefine({
  title: 'Todos',
  input: '',
  debug: true,
  busy: false,
  count: 0,
  todos: [{ id: 1, text: 'Learn' }, { id: 2, text: 'Build' }],
  matrix: [[1, 2], [3, 4]],
  $tpl: prolit_html`
    <h1>{{ title }}</h1>

    <!-- property + boolean + class/style + event -->
    <button
      @click="count++; $update()"
      ?disabled="busy"
      ~class="{ active: count > 0 }"
      ~style="{ color: busy ? 'gray' : 'blue' }"
    >
      Clicked {{ count }}x
    </button>

    <!-- interpolation in attribute (quoted) -->
    <div title="Items: {{ todos.length }}"></div>

    <!-- multiple structural directives on one element (left-to-right) -->
    <!-- order: *if then *for -> if gates the loop -->
    <ul>
      <li *if="todos.length" *for="t of todos; t.id">
        {{$index}}: {{ t.text }}
      </li>
    </ul>

    <!-- order: *for then *if -> loop first, filter per item -->
    <ul>
      <li *for="t of todos" *if="t.text.startsWith('B')">
        {{ t.text }}
      </li>
    </ul>

    <!-- nested loops by repeating *for -->
    <ul>
      <li *for="row of matrix" *for="cell of row">{{ $index }}:{{ cell }}</li>
    </ul>

    <!-- object iteration with 'in' and $index -->
    <ul>
      <li *for="k in obj">{{ $index }}:{{ k }}={{ obj[k] }}</li>
    </ul>

    <!-- *do and *log -->
    <p *do="greet = 'Hi'">{{ greet }}, user!</p>
    <span *if="debug" *log="todos.length"></span>
  `,
  // additional data used above
  obj: { a: 1, b: 2 },
});

@customElement('todo-list')
export class TodoList extends LitElement {
  constructor() { super(); scope.$this = this; }
  override render() { return scope.$tpl.render(); }
}

Key capabilities

  • Use multiple structural directives on the same element; they apply left-to-right (attribute order).
  • *for supports of (arrays) and in (object keys), exposes $index, and optional keying via ; expr (e.g. t.id).
  • Inline handlers run in scope; for in-place mutations, call $update(). Assigning to non-$ scope fields triggers an update automatically when scope.$this is set.