Registry / web-framework / webpack-production-setup

webpack-production-setup

library5.0.0jsnpmunverified

This package, `webpack-production-setup`, provides a pre-configured Webpack 2 build pipeline aimed at production performance and simplicity. Despite its `5.0.0` version, the documentation explicitly states it targets Webpack 2, making it severely outdated for current Webpack versions (5+). It abstracts common configurations for ES6, Babel, and Sass bundling into a reusable `webpack.config.js` file that can be required and optionally mutated. Its stated focus is on ease of use and optimized output. Given the dependency on Webpack 2 and the last commit dating back to 2017, it is not actively maintained for modern Webpack environments and has not seen recent updates to align with current ecosystem best practices or Webpack 5 features.

web-framework devops

npm install webpack-production-setup

package ↗homepage ↗

INSTALL

IMPORT

SIG · WEBPACK-PRODUCTION

webpack-production-setup

web-frameworkjavascriptv5.0.0

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

webpack.config.js

✓ const wppsConfig = require('webpack-production-setup/webpack.config.js');

✗ import wppsConfig from 'webpack-production-setup/webpack.config.js';

This package exposes a CommonJS configuration file directly. There are no named or default ESM exports. The package name alias 'wpps' can also be used, e.g., `require('wpps/webpack.config.js')`.

This code demonstrates how to import the default Webpack configuration provided by `webpack-production-setup` and then modify it with custom plugins or settings before exporting it for Webpack to consume.

const wppsConfig = require('webpack-production-setup/webpack.config.js'); // Optionally, mutate the configuration provided by the package wppsConfig.plugins.push(/* my own plugins here, e.g., new SomeWebpackPlugin() */); wppsConfig.devtool = 'cheap-module-eval-source-map'; // Example of overriding devtool module.exports = wppsConfig;

Debug

Known issues

breakingThis package is explicitly built for Webpack 2. Attempting to use it with modern Webpack versions (3, 4, 5, or later) will result in significant configuration errors, breaking changes in plugins, and build failures due to API incompatibilities.

fix

Do not use this package for projects requiring Webpack versions beyond 2. Consider creating a new Webpack configuration from scratch or using a modern starter kit.

affects: >=3.0.0

gotchaThe README itself warns that the setup 'might not work everywhere'. This indicates that even within its intended Webpack 2 environment, it may not be robust enough for diverse project structures or specific use cases.

fix

Thoroughly test the generated build and configuration in your specific project environment. Be prepared to manually debug and adjust parts of the configuration.

affects: >=1.0.0

breakingThe package lists extremely old Node.js (`>=5.4.1`) and npm (`>=3.3.12`) engine requirements. Using this package with modern Node.js or npm versions may lead to unexpected behavior, compatibility issues, and potentially security vulnerabilities.

fix

Avoid using this package in environments with modern Node.js or npm. The project is effectively abandoned, and maintaining old Node.js versions solely for this setup is not recommended.

affects: >=1.0.0

Upgrade

Version history

5.0.0latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

13 hits · last 30 days

node

OpenAI (training)

Resources

packagehttps://www.npmjs.com/package/webpack-production-setup ↗

homepagehttps://zeachco.com ↗