From 448fcd4824d948ded762ddc6f0cdc59d143bbd25 Mon Sep 17 00:00:00 2001 From: Even Stensberg Date: Fri, 24 Oct 2025 21:55:42 +0200 Subject: [PATCH] chore: replace old urls --- src/content/concepts/hot-module-replacement.mdx | 2 +- src/content/contribute/writing-a-loader.mdx | 2 +- src/content/migrate/3.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/concepts/hot-module-replacement.mdx b/src/content/concepts/hot-module-replacement.mdx index d596e48d081a..8c99a66a4063 100644 --- a/src/content/concepts/hot-module-replacement.mdx +++ b/src/content/concepts/hot-module-replacement.mdx @@ -44,7 +44,7 @@ The compiler ensures that module IDs and chunk IDs are consistent between these ### In a Module -HMR is an opt-in feature that only affects modules containing HMR code. One example would be patching styling through the [`style-loader`](https://github.com/webpack-contrib/style-loader). In order for patching to work, the `style-loader` implements the HMR interface; when it receives an update through HMR, it replaces the old styles with the new ones. +HMR is an opt-in feature that only affects modules containing HMR code. One example would be patching styling through the [`style-loader`](https://github.com/webpack/style-loader). In order for patching to work, the `style-loader` implements the HMR interface; when it receives an update through HMR, it replaces the old styles with the new ones. Similarly, when implementing the HMR interface in a module, you can describe what should happen when the module is updated. However, in most cases, it's not mandatory to write HMR code in every module. If a module has no HMR handlers, the update bubbles up. This means that a single handler can update a complete module tree. If a single module from the tree is updated, the entire set of dependencies is reloaded. diff --git a/src/content/contribute/writing-a-loader.mdx b/src/content/contribute/writing-a-loader.mdx index 8b3f12caeffb..e7286112a96e 100644 --- a/src/content/contribute/writing-a-loader.mdx +++ b/src/content/contribute/writing-a-loader.mdx @@ -139,7 +139,7 @@ Make sure the loader does not retain state between module transformations. Each ### Loader Utilities -Take advantage of the [`loader-utils`](https://github.com/webpack/loader-utils) package which provides a variety of useful tools. Along with `loader-utils`, the [`schema-utils`](https://github.com/webpack-contrib/schema-utils) package should be used for consistent JSON Schema based validation of loader options. Here's a brief example that utilizes both: +Take advantage of the [`loader-utils`](https://github.com/webpack/loader-utils) package which provides a variety of useful tools. Along with `loader-utils`, the [`schema-utils`](https://github.com/webpack/schema-utils) package should be used for consistent JSON Schema based validation of loader options. Here's a brief example that utilizes both: **loader.js** diff --git a/src/content/migrate/3.mdx b/src/content/migrate/3.mdx index cabd81e004a3..dec239634b6a 100644 --- a/src/content/migrate/3.mdx +++ b/src/content/migrate/3.mdx @@ -267,7 +267,7 @@ Thus make sure to remove the plugin from your configuration: ## ExtractTextWebpackPlugin - breaking change -[ExtractTextPlugin](https://github.com/webpack-contrib/extract-text-webpack-plugin) requires version 2 to work with webpack 2. +[ExtractTextPlugin](https://github.com/webpack/extract-text-webpack-plugin) requires version 2 to work with webpack 2. `npm install --save-dev extract-text-webpack-plugin`