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

webpack-config-dump-plugin

v3.0.3

Published

A webpack plugin to cache compiled webpack config on the file system

Downloads

14,139

Readme

[Webpack plugin] Dump Webpack Config into file system

A webpack plugin to dump compiled webpack config into file system. Is useful in case you have resolve aliases formed dynamically and want your IDE to be able to handle them.

For typescript config file you can use webpack-typescript-config-dump-plugin

MIT License

Installation

npm i webpack-config-dump-plugin --save-dev

Usage

Javascript module

const { WebpackConfigDumpPlugin } = require("webpack-config-dump-plugin");

// webpack config
{
  plugins: [new WebpackConfigDumpPlugin(options)];
}

Typescript module

import { WebpackConfigDumpPlugin } from "webpack-config-dump-plugin";

// webpack config
{
  plugins: [new WebpackConfigDumpPlugin(options)];
}

Options and defaults

| Option | Type | Required | Default | Description | | ---------------------- | ------- | -------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | outputPath | string | no | ./ | Path to store config dump | | name | string | no | webpack.config.dump | Dump filename | | depth | number | no | 4 | Config depth. Since webpack config is circularly locked, we can't dump whole config. This parameter sets how deep config dump will be stored | | keepCircularReferences | boolean | no | false | If true, dumps whole config (disables the "depth" option) and marks parts that are circular references | | showFunctionNames | boolean | no | false | By default functions are excluded from the final dump. If true, plugin marks properties that are functions | | includeFalseValues | boolean | no | false | By default false-ish values are excluded from the dump. If true, plugin will dump empty objects, 0, '' etc |

Changes

  • 3.0.2 Bumped dependencies. Also wildcard the lodash and webpack-log so it accepts any version change from the upstream project

  • Version 3 Added more flexibility, see the options section.
    Introduced some features like keepCircularReferences and so forth
    BREAKING: Adjusted consistency for empty values. Now it does not output empty objects and empty arrays by default (i.e. with includeFalseValues=false). Check the plugin configuration for details.

  • Version 2 In version 2 the plugin has been rewritten using Typescript.
    BREAKING: Now it needs to be imported as ES module. Check the information above for details.