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 🙏

© 2024 – Pkg Stats / Ryan Hefner

puppers

v0.0.1

Published

Progressively enhance your site with a psuedo app-shell experience

Downloads

2

Readme

🐶 Puppers

Static websites are ⚡. App-shells are 💯. Why not have both?

Build your static site. Then add a data-attribute to certain elements and the app-shell will kick in.

Those with JS disabled still get a normal static site experience 🙂

How to Use

  1. <script src="/path/to/app-shell.js"></script>

  2. Init app shell

     const appShell = new AppShell();
     appShell.init();
  3. Page-specific content needs a [data-partial] attribute set to:
    Page title, meta description, and canonical tag are updated by default.

    • [data-partial="head"] for elements in the <head>
    • [data-partial="content"] for the page content (one element only!)
    • [data-partial="footer"] for elements just before </body>
  4. The rest of the elements will not update on page requests and will become the "app shell".

  5. Scripts marked [data-partial] are rehydrated on each route change.
    For sitewide scripts in the "app shell" that need to run on each route change, use:

      window.addEventListener('app:routeChanged', e => {
        console.log(e.detail.route());
        // do something
      });
  6. Elements with a [data-partial] location and [data-partial-persist] attributes will be loaded and kept in DOM on page change. (Note: See the example from number 5 to add an event listener on route change if you would like to remove the element later.)

  7. Profit!