v5.2.0

What's Changed

• Ignore css order conflict by @martinbroos in #146
• chore: upgrade minor deps

Full Changelog: v5.1.0...v5.2.0

v5.1.0

What's Changed

• V5 by @martinbroos in #139
• Make enabling source maps configurable via the builder constructor. by @nieuwenhuisen in #145

For example disabling sourcemaps in production:

const builderConfig = {
    env: nodeEnv,
    sourceMap: !isProduction,
};

New Contributors

• @nieuwenhuisen made their first contribution in #145

Full Changelog: v5.0.0...v5.1.0

v5.0.0

This major release should be straight forward, it is there to safely allow to bump the build dependencies. It does drop support for node 12, we now require a minimum of node 14.

For more info follow the Upgrade Guide

[Changes]

• [breaking change] force new major versions - drops node 12 support
• use public output path of 'auto' by default which is the new webpack recommendation
• upgrade webpack-config-builder build packages
• [breaking change] remove createClassNameGeneratorForCSSLoader in favor of css-loader config settings

Full Changelog: v4.4.0...v5.0.0

v4.4.0

What's Changed

• Add support for webp and avif extensions + use browserslist file as target by @martinbroos in #136

Full Changelog: v4.3.0...v4.4.0

v4.3.0

Support node 16
To make this work, uninstall fibers dependency as it doesn't work with node 16.
This release no longer throws an error when fibers is missing but it is still recommended for older node versions (12, 14) because it speeds of the build time of sass.

Full Changelog: v4.2.1...v4.3.0

v4.2.1

• fix NPM 6 support during production builds by @martinbroos in #132
  Full Changelog: v4.2.0...v4.2.1

v4.2.0

What's Changed

• NPM 7 / 8 support by @martinbroos in #130

Changes should be fully compatible with NPM 6. But you can not use the new workspaces setup when some users still use NPM6.
Also note that NPM7+ uses a different lock file format, so it's best to decide for each project if you want to build it with NPM 6 or use NPM 7/8

Full Changelog: v4.1.0...v4.2.0

v4.1.0

What's Changed

LoadReferencedFileAdapter had some issues when adding extra rules because it would also match the existing asset module rule.
This could lead to problems for example when using SVGR in react.
To fix this we changed this to a oneOf rule and added a new option additionalAssetRules and dropped the test config. As working with loadReferencedFileAdapter would lead to issues we didn't concider this as a breaking change. But still it's recommended that you use the new config option additionalAssetRules instead of pushing rules yourself (see upgrade guide for examples) or changing the test config.

Full Changelog: v4.0.4...v4.1.0

v4.0.4

Bugfix:

• Name of the assets was no longer included in files created by webpack 5 assets modules. Which leads to problems when you want to load the file from the stats.json and want to use in in your html with webpack_asset extension. At Freshheads we use this for preloading fonts.

v4.0.0

This major upgrade moves from Webpack 4 to 5 together with improvements to the adapters. See beta releases for detailed description.

We created an upgrade guide to quickly move from webpack-config-builder 3.x to 4.x.
See UPGRADE-4.0.md

When upgrading please read the migration guide supplied by Webpack. As some settings / best practices are still done at application level.
https://webpack.js.org/migrate/5/