v2.4.0

🚀 Features

• Added --eslintFix and --stylelintFix CLI flags
• Added support for aem.port in addition to crx.port for pom.xml configurations

v3.0.0-beta.11

🐛 Bug Fixes

• Rolled eslint-webpack-plugin back to 2.1.0 to fix build errors

v3.0.0-beta.10

🐛 Bug Fixes

• Fixed the aemdesign-compose executable, it contained Windows line endings 🤔

🧰 Maintenance

• Updated all NPM dependencies to their latest releases

v3.0.0-beta.9

💥 Breaking Changes

• Node.js 12 is now the minimum support version

🧰 Maintenance

• Updated all NPM dependencies to their latest releases

v3.0.0-beta.8

🚀 Features

• Added Vue 3 support
• Features can now have custom options for more refined configuration

💥 Breaking Changes

• Updated the features configuration value to an object rather than an array

🐛 Bug Fixes

• Added missing webpack HMR plugin when hmr flag was set

🧰 Maintenance

• Updated all NPM dependencies to their latest releases

---

Features configuration

The features configuration structure has changed from an array to an object of key/value pairs which enables more refined control. Vue is currently only taking advantage of this but others will follow suit in future updates when it becomes a need for them too. Using Vue as our example, the new structure looks like the below.

module.exports = {
  features: {
    vue: {
      version: 3,
    },
  },
}

You can find all the supported configuration options at the following link: https://github.com/aem-design/npm-compose-webpack/blob/develop/src/types/feature.ts#L28-L81.

For features that don't support options, you can configure them using a boolean value which is a toggle for enabled/disabled or pass an empty object.

module.exports = {
  features: {
    bootstrap: false,
    typescript: true,
    vue: {},
  },
}

v3.0.0-beta.7

🐛 Bug Fixes

• Regenerated yarn.lock to fix any reference issues
• Fixed how the package version is loaded to ensure it works in Yarn workspaces

🧰 Maintenance

• Updated @types/lodash to the latest version

v3.0.0-beta.6

I accidentally published v3.0.0-beta.5 without tagging it as a beta release so we jump from v3.0.0-beta.4 to v3.0.0-beta.6.

🚀 Features

• Updated to the official release of webpack v5
• Set the default target for browserslist and web
• Removed entry from WebpackIgnoredProps due to the new import structure available which allows more control over build outcomes

🐛 Bug Fixes

• Removed OptimizeCSSAssetsPlugin due to no webpack 5 support
• Fixed webpack modules resolver for projects using Yarn workspaces
• Fixed getIfUtilsInstance incorrectly caching itself which cause dev and prod builds to cross over

🧰 Maintenance

• Updated all NPM dependencies to their latest releases

v3.0.0-beta.4

🐛 Bug Fixes

• Fixed built distribution files which were exported into a broken directory structure

v3.0.0-beta.3

🚀 Features

• Updated to webpack v5.0.0-rc.4

🐛 Bug Fixes

• Fixed first-class TypeScript support for compose.config.js
• Fixed built distribution files which were exported into a broken directory structure (fixed in v3.0.0-beta.4)

🧰 Maintenance

• Updated all NPM dependencies to their latest releases

v3.0.0-beta.2

🚀 Features

• Updated to webpack v5.0.0-rc.3

🧰 Maintenance

• Updated all NPM dependencies to their latest releases