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-util

v0.0.10

Published

Imperative control of your webpack config using typesafe, mix and match plugins and generators

Downloads

1

Readme

webpack-config-utils

The Problem

Declarative configuration is great but the learning cost is high for the majority of folk. Sometimes you just want to create a webpack config with a few options and then sprinkle on a few settings.

The Solution

Webpack config util offers 2 methods to create the perfect config:

🛠 Create Config:

We expose a function createConfig which is what you'll need to create a ready-to-go config.

Its options are intuitive yet support a wide range of scenarios including node/web, dev servers or even logging of emitted bundle sizes

Full list of options here

🩹 Plugins:

A grab bag of imperative "plugins" that understand the config they're operating on. Just stack them up according to your use case

We have found for our projects this really helps with auditing what it is we want our bundler to actually do for us. It's far too easy for codebases and bundler configs to get out of sync

The plugins are also compatible with next plugins although tend to be a little lower level

Installation

This module is distributed via npm which is bundled with node and should be installed as one of your project's devDependencies:

yarn add -D @peartree/webpack-config-util

Usage

This example uses typescript configuration but feel free to use a webpack.config.js file

// webpack.config.ts
import {plugins, getDevPackagesPaths, compose, createConfig} from '@peartree/webpack-config-util'

const composedPlugins = compose(
  plugins.mainFields(['ts', 'tsx', 'js']),
  plugins.whitelistAllPackages(),
)

const config = composedPlugins(createConfig({}))

export default config

Again, this assumes a webpack.config.ts. For JS configs, drop the TS_NODE_FILES env

// package.json
{
  ...
  "scripts": {
    "dev": "NODE_ENV=development TS_NODE_FILES=true build-webpack-development --verbose",
    "build": "NODE_ENV=production TS_NODE_FILES=true build-webpack-production"
  }
}

Command line docs are here

Options

| parameter | web/node | default | type | description | |-------|----|-------------------------------------------|:---:|---:| | nodeBundle | node | index | string | the name of the bundle file | | buildDir | node | dist | string | where the bundle will be output to | | host | node | localhost | string | where the bundle will be output to | | port | node | 3000 | number | where the bundle will be output to | | serverEntryPoint | web & node | (src/)index.js | string | entry point relative to ./src directory | | hotModuleReplacement | web | true | boolean | whether to apply the hot module replacement plugin | | mode | web & node | required | 'development' or 'production' | defines whether webpack will operate in dev mode. Note this is distinct from NODE_ENV | | target | web & node | required | 'web' or 'node' | defines the target platform target |

Command Line

| parameter | description | |---------------------:|--------------------------:| | verbose | logs the full config to the console

Plugins

TBD. You can check them all here

Contributing

This package is part of a monorepo. Please see here for details of how to contribute.

The project follows the all-contributors specification. Contributions of any kind welcome!