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

metalsmith-asset-references

v0.1.1

Published

A Metalsmith plugin that replaces references to assets in your sources with hashed or fingerprinted references generated by another plugin

Readme

Metalsmith Asset References

A Metalsmith plugin that replaces references to assets in your sources with hashed or fingerprinted references generated by another plugin

Installation

npm install metalsmith-asset-references

Explanation

I became frustrated when using some of Metalsmith’s plugins for asset hashing (eg metalsmith-contenthash, metalsmith-fingerprint). These plugins provide a metadata object for looking up hashes, which can be used in templates as follows:

<img src='{{ hashes["/images/image.png"] }}'>

This works fairly easily for references in markup files, but when you get to CSS files and their corresponding SASS/PostCSS/whatever workflow, and JS files and their corresponding Uglify/Webpack/whatever workflow, things get a little hairier! Sometimes you can use some Handlebars templating in the right part of your build process to get hashed references into CSS and JS files, and sometimes you can’t.

Instead, this plugin does a simple find and replace on your sources — finding any asset references by simple string comparison and swapping them out with the hashed versions. The main benefit here is there’s no special helper syntax specific to one templating language, so these references can go in any type of file without causing syntax errors (and then I discovered Spike...)

Usage

Add the plugin after your asset hashing plugin of choice. Then references images in any file from the project root with no special syntax.

metalsmith(__dirname)
  .source("source")
  .use(contenthash({ "**/*.{png,jpg,svg,js,css,woff,woff2}" }))
  .use(references({ key: "hashes" })) // Change to "fingerprint" for metalsmith-fingerprint
  // ...

index.html (before)

<!doctype html>
<html>
  <head>
    <link rel="stylesheet" href="/styles/style.css">
  </head>
  <body>
    <img src="/images/image.png">
    <script src="/scripts/script.js"></script>
  </body>
</html>

index.html (after)

<!doctype html>
<html>
  <head>
    <link rel="stylesheet" href="/styles/style.ed7fd542688e317a.css">
  </head>
  <body>
    <img src="/images/image.e3b0c44298fc1c14.png">
    <script src="/scripts/script.b6ed35f5ae339a35.js"></script>
  </body>
</html>