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

websmith-loader

v0.8.5

Published

A webpack loader for the websmith compiler

Readme

websmith-loader

A drop-in replacement for the ts-loader to add the websmith compiler to your build and bundling process. Websmith provides an API to create compiler addons to modify the compilation input before, during and after compiled artifacts are created, compilation profiles to specify individual environments for different outputs, and integrates seamlessly with webpack build commands.

Visit the websmith github repository for more information and examples.

Getting started

Whenever you use the ts-loader to compile your TypeScript project, you can replace it with the websmith-loader command and apply compiler addons.

Installation

Add the loader to your TypeScript project with the websmith-loader package. For example, use the following command with pnpm:

pnpm add --dev websmith-loader

Use websmith-loader in your webpack configuration

You can use the websmith-loader loader in your webpack configuration by adding the following entry to your module.rules configuration:

// ./webpack.config.js
const { join } = require("path");

module.exports = {
    // ...
    module: {
        rules: [
            {
                test: /\.(?:[j|t]sx?)$/,
                use: [
                    {
                        loader: "websmith-loader",
                        options: {
                            tsConfigFile: join(__dirname, "tsconfig.json"),
                            config: {
                                addonsDir: join(__dirname, "addons"),
                                addons: ["export-yaml-generator"],
                            },
                            transpileOnly: true,
                            addonEmitOnly: false, // Set to true to only emit files processed by addons
                        },
                    },
                ],
            },
            // ...
        ],
    },
};

The default configuration uses the tsconfig.json file in your project root to compile the TypeScript files. Add a custom compilation config to the loader options or use the websmith.config.json file to configure the compilation output.

Loader Options

  • tsConfigFile (string): Path to the TypeScript configuration file
  • config (object): Websmith configuration (can also be loaded from websmith.config.json)
  • transpileOnly (boolean): Enable transpile-only mode for faster builds without type checking
  • addonEmitOnly (boolean): Only emit files that are processed by active addons. When enabled, all files are still compiled for dependencies and type checking, but only files processed by addon callbacks (generators, processors, transformers) are written to disk. This is useful for code generation workflows where you want to preserve original source files unchanged while emitting only generated or transformed files.
  • profile (string): Name of the compilation profile to use

Add websmith configuration

You can use a websmith.config.json file to configure which addons should be used for what profile by websmith during the webpack compilation process:

// websmith.config.json
{
    "profiles": {
        "executeAddons": {
            "addons": ["my-addon"],
        },
    }
}

Note: The webpack loader will expect a profile called executeAddons which we need to configure in the webpack configuration.

Read more about compilation profiles in the websmith compiler documentation. Or check out more details on the configuration file in the compiler documentation.