Handling Configurations

Configurations are handled slightly differently compared to the Angular CLI. Rsbuild and Rspack use mode instead of configurations to handle different environments by default. This means that a different solution is needed to handle different build configurations you may have to match the behavior of Angular's configuration handling.

@ng-rsbuild/plugin-angular provides a withConfigurations function to help you handle this. It uses the NGRS_CONFIG environment variable to determine which configuration to use. The default configuration is production.

Using withConfigurations

The withConfigurations function takes two arguments, the first is the default options, and the second is an object of configurations. The configurations object is keyed by the name of the configuration, and the value is an object with the options and rsbuildConfigOverrides to be used for that configuration.

    rsbuild.config.ts
  
import { withConfigurations } from '@ng-rsbuild/plugin-angular';
export default withConfigurations({
  options: {
    browser: './src/main.ts',
    server: './src/main.server.ts',
    ssrEntry: './src/server.ts',
  },
  rsbuildConfigOverrides: {
    plugins: [pluginSass()],
  },
}, {
  production: {
    options: {
      fileReplacements: [
        {
          replace: './src/environments/environment.ts',
          with: './src/environments/environment.prod.ts',
        },
      ],
    },
  },
});

The above example shows how to handle the production configuration. The options are the same as the default options, and the rsbuildConfigOverrides are the same as the default rsbuildConfigOverrides but with the fileReplacements property added.

The NGRS_CONFIG environment variable is used to determine which configuration to use. If the environment variable is not set, the production configuration is used by default.
If a production configuration is not provided, the default configuration is used.

To run the build with the production configuration:

NGRS_CONFIG=production npx rsbuild build