clean experiments.importAwait and experiments.importAsync (#3892)

Author: chenxsan

src/content/configuration/experiments.md

@@ -21,8 +21,6 @@ Available options:
 - `syncWebAssembly`: Support the old WebAssembly like in webpack 4
 - `asyncWebAssembly`: Support the new WebAssembly according to the [updated specification](https://github.com/WebAssembly/esm-integration), it makes a WebAssembly module an async module
 - `topLevelAwait`: Support the [Top Level Await Stage 3 proposal](https://github.com/tc39/proposal-top-level-await), it makes the module an async module when `await` is used on the top-level
-- `importAsync`: import async modules with `import`
-- `importAwait`: import async modules with `import await`
 - `asset`: a type of module that allows to use asset files (fonts, images, etc) without configuring loaders to handle their importing, similar to `file-loader` | `url-loader` | `raw-loader`
 - `outputModule`: enables the use of [`output.module`](/configuration/output/#outputmodule) configuration option and sets it to `true`. Enables the use of `output.libraryTarget` as `'module'` and sets it to `'module'`.
 
@@ -38,8 +36,6 @@ module.exports = {
     topLevelAwait: true,
     asset: true,
     asyncWebAssembly: true,
-    importAsync: true,
-    importAwait: true,
   },
 };
 ```

src/content/configuration/externals.md

@@ -319,8 +319,8 @@ Supported types:
 - `'umd2'`
 - `'jsonp'`
 - `'system'`
-- `'promise'` - same as `'var'` but awaits the result (async module, depends on [`experiments.importAsync`](/configuration/experiments/))
-- `'import'` - uses `import()` to load a native EcmaScript module (async module, depends on [`experiments.importAsync`](/configuration/experiments/))
+- `'promise'` - same as `'var'` but awaits the result (async module)
+- `'import'` - uses `import()` to load a native EcmaScript module (async module)
 
 __webpack.config.js__
 

src/content/migrate/5.md

@@ -106,7 +106,7 @@ Yarn: `yarn add webpack@next -D`
 If you were using WASM 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.
-- After successful migration to webpack 5, change the `experiments` value to `experiments: { asyncWebAssembly: true, importAsync: true }` to use the up-to-date spec for WASM integration.
+- After successful migration to webpack 5, change the `experiments` value to `experiments: { asyncWebAssembly: true }` to use the up-to-date spec for WASM integration.
 
 Reconsider `optimization.splitChunks`: