miel.truyen/nx
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

docs(angular): use @nx/angular:dev-server instead of legacy @nx/angular:webpack-dev-server (#20637)

Browse Source
This commit is contained in:
Nikita Barsukov 2023-12-12 17:55:06 +03:00 committed by GitHub
parent d36f313776
commit 332b0120df
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/shared/guides/module-federation/dynamic-mfe-angular.md
View File

@ -99,7 +99,7 @@ For both applications, the generator did the following:
- Moved the code that is normally in `main.ts` to `bootstrap.ts`
- Changed `main.ts` to dynamically import `bootstrap.ts` _(this is required for the Module Federation to correct load versions of shared libraries)_
- Updated the `build` target in the `project.json` to use the `@nx/angular:webpack-browser` executor _(this is required as it supports passing a custom Webpack configuration to the Angular compiler)_
- Updated the `serve` target to use `@nx/angular:webpack-dev-server` _(this is required as we first need Webpack to build the application with our custom Webpack configuration)_
- Updated the `serve` target to use `@nx/angular:dev-server` _(this is required as we first need Webpack to build the application with our custom Webpack configuration)_
The key differences reside within the configuration of the Module Federation Plugin within each application's `module-federation.config.js`.

2
docs/shared/guides/use-environment-variables-in-angular.md
View File

@ -54,7 +54,7 @@ Next, update the `build` and `serve` targets (in `project.json` or `angular.json
},
"serve": {
// NOTE: use dev-server that supports custom webpack config.
"executor": "@nx/angular:webpack-dev-server"
"executor": "@nx/angular:dev-server"
// snip
}
}