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

rollup-plugin-hash

v1.3.0

Published

Rollup plugin to add a checksum to your destination filename

Downloads

3,990

Readme

rollup-plugin-hash Travis Build Status

Rollup plugin to compose bundle output filenames with unique hashes, to facilitate long-term caching of your static resources.

It uses is simple placeholder pattern to substitue filename with bundle hash. I.e.

main.[hash].js

becomes:

main.07d2bf0d12655d9f51c0637718da4889.js

Install

via npm:

npm install --save-dev rollup-plugin-hash

via yarn:

yarn add --dev rollup-plugin-hash

Usage

import { rollup } from 'rollup';
import hash from 'rollup-plugin-hash';

rollup({
    entry: 'main.js',
    plugins: [
        hash({ 
			dest: 'main.[hash].js'	
		})
    ]
});

Meanwhile, if dest filename is written the following way, only first 4 characters of hash will be used in final filename: main.[hash:4].js. You could change this number to modify the output result.

Options

dest

Type: string Required: true

The template of your filename destination. Must include the placeholder [hash] to be replaced.

replace

Type: boolean Default: false Required: false

Whether the hashed version should replace the main output file generated by Rollup. Useful in CI environments where you don't need any non-hashed assets.

algorithm

Type: string Default: sha1 Required: true

Hashing algorithm used to generate hash. Can be one of md5, sha1, sha256, sha512

manifest

Type: string Required: false

Filename to write a manifest to. Will generate a JSON manifest mapping input filename to hashed output filename. Useful if you want to dynamically generate link to your hashed output server-side.

Example manifest:

{
	"main.js": "main.56770a64be1a1132502b276c4132a76bb94d9e1b.js"
}

manifestKey

Type: string Default: bundle.dest Required: false

The filename used as the input key in the generated manifest map. Useful in certain build setups where path.resolve is needed as bundle.dest but not in the manifest.

callback

Type: function Required: false

Callback which is called with the resulting hashed filename. This is useful if you are integrating with other build steps and want to store the filename locally to be used in subsequent configs etc.

License

MIT ©