@nx/react:remote
Create Module Federation configuration files for given React Remote Application.
Create Module Federation configuration files for given React Remote Application.
1nx generate remote ...
2
By default, Nx will search for remote
in the default collection provisioned in workspace.json.
You can specify the collection explicitly as follows:
1nx g @nx/react:remote ...
2
Show what will be generated without writing to disk:
1nx g remote ... --dry-run
2
The directory of the new application.
rspack
rspack
, webpack
The bundler to use.
The port for the dev server of the remote app.
The host / shell application for this remote.
^[a-zA-Z_$][a-zA-Z_$0-9]*$
The name of the remote application to generate the Module Federation configuration
false
Use class components instead of functional component.
babel
babel
, swc
The compiler to use.
playwright
playwright
, cypress
, none
Test runner to use for end to end (E2E) tests.
false
Default is false. When true, the component is generated with .css/.scss instead of .module.css/.module.scss.
false
Generate JavaScript files rather than TypeScript files.
eslint
eslint
The tool to use for running lint checks.
false
Generate application with routes.
css
The file extension to be used for style files.
true
Creates an application with strict mode and strict type checking.
false
Whether or not to configure the ESLint "parserOptions.project" option. We do not do this by default for lint performance reasons.
false
Whether to configure SSR for the host application
Add tags to the application (used for linting).
true
Whether the module federation configuration and webpack configuration files should use TS. When --js is used, this flag is ignored.
jest
jest
, none
Test runner to use for unit tests.
false
Should the host application use dynamic federation?
false
Skip formatting files.
false
Skip updating nx.json with default options based on values provided to this app (e.g. babel, style).
false
Do not add dependencies to package.json
.