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 🙏

© 2026 – Pkg Stats / Ryan Hefner

jsx-webpack-plugin

v1.0.0

Published

Renders your jsx-template on build time

Readme

Server-side template rendering using JSX

npm install react react-dom @babel/core @babel/preset-env @babel/preset-react jsx-webpack-plugin --save-dev

Usage

In your webpack config register and setup the jsx plugin

const path = require("path");
const JSXPlugin = require("jsx-webpack-plugin");

const webpackConfig = {
    plugins: [
        new JSXPlugin({
            // path to hbs entry file(s). Also supports nested directories if write path.join(process.cwd(), "app", "src", "**", "*.jsx"),
            entry: path.join(process.cwd(), "app", "src", "*.jsx"),
            // output path and filename(s). This should lie within the webpacks output-folder
            // if ommited, the input filepath stripped of its extension will be used
            output: path.join(process.cwd(), "build", "[name].html"),
            // you can also add a [path] variable, which will emit the files with their relative path, like
            // output: path.join(process.cwd(), "build", [path], "[name].html"),

            // globbed path to components to watch for changes
            partials: [
                path.join(
                    process.cwd(),
                    "app",
                    "src",
                    "components",
                    "*",
                    "*.jsx"
                ),
            ],

            // hooks
            // getTargetFilepath: function (filepath, outputTemplate) {},
            // getPartialId: function (filePath) {}
            onBeforeSetup: function () {},
            onBeforeRender: function (data, filename) {},
            onBeforeSave: function (resultHtml, filename) {},
            onDone: function (filename) {},
        }),
    ],
};

Options

target filepaths

Per default, the generated filepath of the html-results is defined by the output-property in the plugin-options. To changed the output folder and name, you can pass your custom filepath-helper to the plugin-options like

{
    /**
     * Modify the default output path of each entry-template
     * @param {String} filepath     - the source of the template
     * @param {String} outputTemplate - the filepath template defined in `output`
     * @param {String} rootFolder   - the filepaths rootFolder
     * @return {String} final path, where the rendered html-file should be saved
     */
    getTargetFilepath: function getTargetFilepath(
        filepath,
        outputTemplate,
        rootFolder
    ) {
        const fileName = path
            .basename(filepath)
            .replace(path.extname(filepath), "");
        return outputTemplate.replace("[name]", fileName);
    }
}

You can find the default implementation in utils/getTargetFilepath.