DEPRECATED for webpack v5: please use output.filename instead.

Webpack plugin for creating custom path template tags. Extend the default set of template tags with your own custom behavior. Hooks into Webpack’s compilation process to allow you to replace tags with a substitute value.


Install the module

npm install @wordpress/custom-templated-path-webpack-plugin --save-dev

Note: This package requires Node.js 12.0.0 or later. It is not compatible with older versions. It works only with webpack v4.


Construct an instance of CustomTemplatedPathPlugin in your Webpack configurations plugins entry, passing an object where keys correspond to the template tag name. The value for each key is a function passed the original intended path and data corresponding to the asset.

The following example creates a new basename tag to substitute the basename of each entry file in the build output file. When compiled, the built file will be output as build-entry.js.

const { basename } = require( 'path' );
const CustomTemplatedPathPlugin = require( '@wordpress/custom-templated-path-webpack-plugin' );

module.exports = {
    // ...

    entry: './entry',

    output: {
        filename: 'build-[basename].js',

    plugins: [
        new CustomTemplatedPathPlugin( {
            basename( path, data ) {
                let rawRequest;

                const entryModule = get( data, [ 'chunk', 'entryModule' ], {} );
                switch ( entryModule.type ) {
                    case 'javascript/auto':
                        rawRequest = entryModule.rawRequest;

                    case 'javascript/esm':
                        rawRequest = entryModule.rootModule.rawRequest;

                if ( rawRequest ) {
                    return basename( rawRequest );

                return path;
        } ),

For more examples, refer to Webpack’s own TemplatedPathPlugin.js, which implements the base set of template tags.

Contributing to this package

This is an individual package that’s part of the Gutenberg project. The project is organized as a monorepo. It’s made up of multiple self-contained software packages, each with a specific purpose. The packages in this monorepo are published to npm and used by WordPress as well as other software projects.

To find out more about contributing to this package or Gutenberg as a whole, please read the project’s main contributor guide.