feat: Added codemods for migrating webpack from v4 to v5

src/content/migrate/5.mdx

@@ -12,6 +12,7 @@ contributors:
   - jamesgeorge007
   - getsnoopy
   - yevhen-logosha
+  - akash-kumar-dev
 ---
 
 This guide aims to help you migrating to webpack 5 when using webpack directly. If you are using a higher level tool to run webpack, please refer to the tool for migration instructions.
@@ -35,6 +36,24 @@ Webpack 5 requires at least Node.js 10.13.0 (LTS), so make sure you upgrade your
    Some Plugins and Loaders might have a beta version that has to be used in order to be compatible with webpack 5.
    Make sure to read release notes of each individual plugin/loader when upgrading it, since latest version might only support webpack 5 and will fail in v4. In such case, it's recommended to update to the latest version that supports webpack 4.
 
+
+## Codemods
+
+To assist with the upgrade webpack from v4 to v5, we have added features that utilize codemods to automatically update your code to many of the new APIs and patterns. Run the following command to automatically update your code for webpack v5 migration:
+
+```bash
+npx codemod webpack/v5/migration-recipe
+```
+
+This will run the following codemods from the webpack Codemod repository:
+
+- **webpack/v5/set-target-to-false-and-update-plugins**
+- **webpack/v5/migrate-library-target-to-library-object**
+- **webpack/v5/json-imports-to-default-imports**
+
+Each of these codemods automates the changes listed in the v5 migration guide. For a complete list of available webpack codemods and further details, see the [codemod registry](https://codemod.com/registry?q=webpack).
+
+
 ### Make sure your build has no errors or warnings
 
 There might be new errors or warnings because of the upgraded versions of `webpack`, `webpack-cli`, Plugins and Loaders. Keep an eye for deprecation warnings during the build.
@@ -126,6 +145,14 @@ If you were not able to upgrade some plugins/loaders to the latest in Upgrade we
   }
   ```
 
+  > **Note**: Codemod for this Chnages:
+  >
+  > ```bash
+  > npx codemod set-target-to-false-and-update-plugins
+  > ```
+  >
+  > (See the [registry here](https://codemod.com/registry/webpack-v5-set-target-to-false-and-update-plugins).)
+
 - If you have output.library or output.libraryTarget defined, change the property names: (output.libraryTarget -> output.library.type, output.library -> output.library.name). Example
 
   ```json
@@ -148,6 +175,14 @@ If you were not able to upgrade some plugins/loaders to the latest in Upgrade we
   }
   ```
 
+  > **Note**: Codemod for this Chnages:
+  >
+  > ```bash
+  > npx codemod webpack/v5/migrate-library-target-to-library-object
+  > ```
+  >
+  > (See the [registry here](https://codemod.com/registry/webpack-v5-migrate-library-target-to-library-object).)
+
 If you were using WebAssembly via import, you should follow this two step process:
 
 - Enable the deprecated spec by setting `experiments.syncWebAssembly: true`, to get the same behavior as in webpack 4.
@@ -204,6 +239,14 @@ import pkg from './package.json';
 console.log(pkg.version);
 ```
 
+  > **Note**: Codemod for this Chnages:
+  >
+  > ```bash
+  > npx codemod codemod webpack/v5/json-imports-to-default-imports
+  > ```
+  >
+  > (See the [registry here](https://codemod.com/registry/webpack-v5-json-imports-to-default-imports).)
+
 #### Cleanup the build code
 
 - When using `const compiler = webpack(...);`, make sure to close the compiler after using it: `compiler.close(callback);`.