@nrwl/react:remote
Create Module Federation configuration files for given React Remote Application.
Create Module Federation configuration files for given React Remote Application.
nx generate remote ...
By default, Nx will search for remote in the default collection provisioned in workspace.json.
You can specify the collection explicitly as follows:
nx g @nrwl/react:remote ...
Show what will be generated without writing to disk:
nx g remote ... --dry-run
^[a-zA-Z].*$The name of the remote application to generate the Module Federation configuration
The directory of the new application.
4200The port for the dev server of the remote app.
The host / shell application for this remote.
falseUse class components instead of functional component.
babelbabel, swcThe compiler to use.
cypresscypress, noneTest runner to use for end to end (e2e) tests.
falseDefault is false. When true, the component is generated with .css/.scss instead of .module.css/.module.scss.
falseGenerate JavaScript files rather than TypeScript files.
eslinteslintThe tool to use for running lint checks.
falseUse pascal case component file name (e.g. App.tsx).
falseGenerate application with routes.
cssThe file extension to be used for style files.
trueCreates an application with strict mode and strict type checking.
falseWhether or not to configure the ESLint "parserOptions.project" option. We do not do this by default for lint performance reasons.
falseWhether to configure SSR for the host application
Add tags to the application (used for linting).
jestjest, noneTest runner to use for unit tests.
falseSkip formatting files.
falseSkip updating workspace.json with default options based on values provided to this app (e.g. babel, style).
trueSplit the project configuration into <projectRoot>/project.json rather than including it inside workspace.json
Nx only supports standaloneConfig