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

@ywmail-pack/webpack-dynamic-hash

v0.0.2

Published

Webpack plugin that allows to configure dynamic hash

Downloads

6

Readme

webpack-dynamic-hash

Webpack plugin that allows to configure dynamic hash

  • Compatible with webpack 4, 3, 2
  • Lightweight
  • No dependencies
  • Tested
  • Production-ready

Why is it helpful?

Webpack allows to atomatically split code to chunks and add hash to file name.

For example

    chunkFilename: 'chunk-[name]-[hash].js',

will result in chunk-name-xxxx.js

but sometimes I need the hash to be a variable, for example:

chunk-name-[GLOBAL.version].js

Global.version is a variable and only to be invoked at runtime, when it changes, the browser will load a different chunk.

How to use

// webpack.config.js
const WebpackDynamicHash = require("webpack-dynamic-hash");
const WebpackDynamicHashConfig = {
  // see configuration options below
};
module.exports = {
  output: {
    filename: "[name].js",
    chunkFilename: "[name]-[hash].js"
  },
  plugins: [new WebpackDynamicHash(WebpackDynamicHashConfig)]
};

Configuration

If no options provided, the default config.output.publicPath will be used.

methodName

Name of the globaly defined method that will be invoked at runtime, the method should return a string that will be used for dynamically importing of chunks.

For example, if chunk name is 0.js and options object is {methodName: "getVersion" }, while window.getVersion is defined to be:

window.getVersion = function() {
  if (true) {
    // use any condition to choose the URL
    return "0.0.0";
  }
};

the chunk will be fetched from https://app.cdn.com/0-0.0.0.js

variableName

Just like methodName, variableName is the globaly defined variable that will be invoked at runtime, the variableName is a string that will be used to replace the hash placeholder for dynamically importing of chunks.

For example, if default URL is https://localhost, chunk name is 0.js and options object is {variableName: "GLOBAL.version" }, while window.GLOBAL.version is defined to be:

window.GLOBAL.version = "0.0.0";

the chunk will be fetched from https://app.cdn.com/0-0.0.0.js

Defining gobaly available methods and variable

When your JS code is executed in browser, the variable/methods whose names you mention as variableName, methodName should be set before the first call to require.ensure() or import() is executed.

The return value of the methods will be used to build the URL for fetching resources.

For example, let's define veryFirst method to be globally available before you main bundle is being executed.

Add the method definition at the very first line of you bundle:

const window.veryFirst = function () {
 console.log("I am very first!");
}

You can use a separate file and use webpack's entry point list:

// filename: veryFirst.js
const window.veryFirst = function () {
 console.log("I am very first!");
}

// file webpack.config.js
module.exports = {
  entry: {
    ['./veryFirst.js', './index.js']
  }
}

Another approach is to define veryFirst as part of index.html when building it on your server:

// filename: server/app.js
app.get("/", (req, res) =>
  res.render("views/index", {
    cdnPath: "https://qa.cdn.com/|https://prod.cdn.com/"
  })
);
<!-- filename: views/index.ejs -->
<html>
<script>
  const baseCDN = "<%= cdnPath %>";
  window.veryFirst = function () {
      console.log(`${baseCDN}/js/`);
  }
</script>
...
</html>

Troubleshooting

Don't hesitate to open issues.

Tests

yarn test