Microfrontends Configuration

The file is used to configure your microfrontends. If this file is not deployed with your default application, the deployment will not be a microfrontend.

See the OpenAPI specification for the microfrontends.json file.

If the application name differs from the field in for the application, you should either rename the name field in to match or add the field to the microfrontends configuration.

The microfrontends configuration file can be named either or .

You can also define a custom configuration file by setting the environment variable — for example, . The file name must end with either or , and it may include a path, such as . The filename / path specified is relative to the root directory for the default application.

Be sure to add the environment variable to all projects within the microfrontends group.

Using a custom file name allows the same repository to support multiple microfrontends groups, since each group can have its own configuration file.

If you're using Turborepo, define the environment variable outside of the Turbo invocation when running , so the local proxy can detect and use the correct configuration file.