The module-federation-dev-server executor is reserved exclusively for use with host Module Federation applications. It allows the user to specify which remote applications should be served with the host.
Options can be configured in
project.json when defining the executor, or when invoking it. Read more about how to configure targets and executors here: https://nx.dev/configuration/projectjson#targets.
List of hosts that are allowed to access the dev server.
A browser builder target to serve in the format of
project:target[:configuration]. You can also pass in more than one configuration name as a comma-separated list. Example:
Don't verify connected clients are part of allowed hosts.
List of remote applications to run in development mode (i.e. using serve target).
Host to listen on.
Custom HTTP headers to be added to all responses.
Enable hot module replacement.
Whether to reload the page on change, using live-reload.
Opens the url in default browser.
Port to listen on.
Proxy configuration file. For more information, see https://angular.io/guide/build#proxying-to-a-backend-server.
The URL that the browser client (or live-reload client, if enabled) should use to connect to the development server. Use for a complex dev server setup, such as one with reverse proxies.
Enable and define the file watching poll time period in milliseconds.
Serve using HTTPS.
SSL key to use for serving HTTPS.
SSL certificate to use for serving HTTPS.
The pathname where the app will be served.
Adds more details to output logging.
Rebuild on change.