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

@goodthnx/metalsmith-webpack

v1.2.2

Published

A glob-based Webpack plugin for Metalsmith.

Downloads

9

Readme

Metalsmith Webpack

A Webpack plugin for Metalsmith.

This is a bit different to existing metalsmith-webpack plugins:

  • a plugin should not write any files itself
  • a plugin should accept the files given to it
  • a plugin should not have 'webpack' as a direct dependency

As a result, this plugin may not suit everyone's use-cases.

Important things

This plugin will ignore both entry and output fields of a webpack config file.

The entry set

This plugin will dynamically create an entry set based on files filtered by the given glob pattern parameter.

Note; it'll only create entries for files that exist. If the pattern doesn't match any files, it will throw an error.

For example:

pattern: "js/{index,utils}.js"
// would become
entry: {
    index: '/.../js/index.js',
    utils: '/.../js/utils.js',
}

Perhaps we could just loop through the entry set and test each against the internal files map. But patterns are simpler and my use-case doesn't require it. When this someone needs it, it will be written.

(although only after the 'output chunks' feature is written, currently the output files rely on the pattern field too.)

The output field

The output field is irrelevant, considering files are written by Metalsmith and not Webpack. Instead, this plugin will only write files that match the pattern field.

This means any the output files are also reliant on the 'pattern' field. Additional output files, like .map, manifest.json, .html or vendor and async files will be lost.

In future, this can resolved by instead using the stats.chunks output from Webpack instead.

Usage

const webpack = require('metalsmith-webpack')

new Metalsmith(__dirname)
.use(webpack({
    pattern: '**/*.{sss,css}',
    config: './webpack.config.js',
    // 'config' AND/OR inline (these will override config file settings)
    devtool: 'inline',
    module: {
        rules: [
            etc...
        ]
    }
}))
.build(err => {
    if (err) throw err;
})