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

lit-html-free

v0.0.1-alpha.14

Published

lit html tools

Downloads

3

Readme

@lit-html-free/{packages}

Custom mono repo for :

Development on current packages

  • Run npm install
  • see how to run samples and start coding

Work in progress - not using lerna for mono repo.

Fusebox is in watch mode when running the samples. Any changes to packages/* files triggers rebuild in fusebox.

HMR is enabled during the samples.

Add new package

  • copy folder ./packages/template-package and give it a new name
  • update name in package.json
  • update description in package.json
  • make a new sample- see how to make a new sample

To run samples

You need to read development first before trying to run these.

  • npm run core-sample
  • npm run grid-sample
  • npm run router-sample
  • npm run realworld-sample

Make new sample

  • copy folder ./samples/template-starter and give it a new name
  • add script to package.json to start it (look at the others for how)

To build all packages

  • Set new package version in root package.json
  • Run npm run build - this will now build all packages and sync package json version in all.

To publish all packages

  • Run pub-now to publish
    • Or pub-test to run publish with --dry-run option

HMR info

When using the samples all of the @lit-html-free packages also gets reset. But this will not be the case if you use them in your own project.

Here is how the hmr.ts file need to look like to reset the router. You dont need to use clearInstance(null) but might be useful to reset everything.

import { applyPolyfill, reflowDOM } from 'custom-elements-hmr-polyfill';
import { clearInstance } from '@lit-html-free/core';
import { getRouter } from '@lit-html-free/router';

//cleanup
getRouter().cleanUp(true);
clearInstance(null);

// apply polly fill
applyPolyfill();

//reflow app
reflowDOM();