blog: enhance Plugin Validation section with detailed explanation and examples

Author: bjohansebas

src/content/blog/2026-03-22-webpack-5-106.mdx

@@ -19,13 +19,18 @@ Explore what's new in this release:
 
 ## Plugin Validation with `compiler.hooks.validate`
 
-Webpack adds a new top level `validate` option to enable or disable schema validation for webpack configuration, plugin options, and loader options. When validation is disabled, webpack skips these checks, which can reduce overhead in some scenarios, but it also removes important guardrails. Invalid options may only fail later or lead to unexpected behavior.
+Webpack adds a new top-level `validate` option and a `compiler.hooks.validate` hook that standardize how schema validation works across webpack configuration, plugins, and loaders.
 
-This change also introduces an internal API so plugins can register validation through `compiler.hooks.validate` and run it with `compiler.validate(...)`, allowing validation behavior to be consistently controlled by the single `validate` flag.
+Until now, there was no unified way for plugins to integrate schema validation into the webpack build lifecycle. Each plugin handled validation on its own. The new `compiler.hooks.validate` hook gives plugin authors a standard API to register their validation logic, and `compiler.validate(...)` to run it. This means all validation (from webpack's core config to every plugin that adopts the hook) is controlled by a single `validate` flag and follows the same patterns:
 
-**Defaults**
+```js
+module.exports = {
+  // Disable schema validation (webpack config, plugins, and loaders)
+  validate: false,
+};
+```
 
-The default value of `validate` depends on the build mode and whether `experiments.futureDefaults` is enabled:
+The default value depends on the build mode:
 
 | Mode        | `experiments.futureDefaults` | Default `validate` |
 | ----------- | :--------------------------: | :----------------: |
@@ -34,18 +39,7 @@ The default value of `validate` depends on the build mode and whether `experimen
 | production  |           `false`            |       `true`       |
 | production  |            `true`            |      `false`       |
 
-**Config example**
-
-```js
-module.exports = {
-  // Disable schema validation (webpack config, plugins, and loaders)
-  validate: false,
-
-  // ...rest of config
-};
-```
-
-**Plugin authoring example (respecting `validate: false`)**
+For plugin authors, integrating validation is straightforward. Register a tap on `compiler.hooks.validate`, and webpack takes care of the rest — including skipping validation entirely when the user sets `validate: false`:
 
 ```js
 class MyPlugin {
@@ -70,6 +64,10 @@ class MyPlugin {
 module.exports = MyPlugin;
 ```
 
+When `validate` is `true` and something is wrong, webpack throws a clear error at compile time.
+
+When `validate` is `false`, that check is skipped entirely. The build may still fail later with a less obvious error, so use this option with care.
+
 ## CSS Modules with Runtime Style Injection
 
 Webpack now supports `exportType: "style"` for CSS Modules (when `experiments.css: true` is enabled), which allows CSS to be injected into the DOM as a `<style>` (`HTMLStyleElement`) directly from the webpack runtime. This covers the typical use case of `style-loader`, so it is no longer necessary to use `style-loader` to inject styles when using this mode.