
# What a build contains

What a build of an application with `spring_boot_starter_flutter_signals` contains, and when something is not in it. A module that follows a key reads it when `build_runner` runs, from `application.yml` or `application.properties` without a profile (see [Modules left out of the build](../spring-core-dart-generator/optimizations/build-conditions.md)). The modules of the packages it depends on come with it: for `spring_boot_dart`, see [Auto-configuration](../spring-boot-dart/auto-configuration.md).

## Always in

No `build:` and no `platform:`: in every build of an application that depends on the starter.

| Module | What it holds |
|---|---|
| `springBootStarterFlutterSignalsAutoConfiguration` | `signalBeans`, `signalBeanNames`, `signalsAdvisor`, `signalEffects` and `signalBuildTracker`: the followed state of every bean with a `@Signal`, `@Computed` or `@Effect` member, and the widgets that build again when it changes. |

## By key

`build: AutoConfigurationBuild(key)`: `true` puts the module in every build, `false` leaves it out with all its code, and when the key is not set the *Not set* column decides.

| Module | Key | Not set | What it holds |
|---|---|---|---|
| `springBootStarterFlutterSignalsDebugAutoConfiguration` | `spring.flutter.signals.debug.enabled` | debug and profile builds only | The state's tab of the debug panel (`signalsDebugSection`): every bean with followed state and its members by name. The tab shows where the debug panel is in the build. |

A module left to `notInRelease` is dropped from Flutter's release builds and from `dart compile exe`. `dart run` and `dart compile js` / `wasm` define no `dart.vm.product`, so there the module stays when the key is not set; only `false` leaves it out.

## What the generator writes for it

A part of the generator (see [Starter parts](../spring-core-dart-generator/how-it-works.md#starter-parts)) runs only when the application reaches its package.

| Part or builder | What it does |
|---|---|
| Signals part (`spring_boot_starter_flutter_signals`) | Writes nothing: fails the build for a `@Signal`, `@Computed` or `@Effect` on a member the bean's proxy cannot follow. The proxy the core writes follows the members at run time. |
| Through its dependencies | The parts and builders of [spring_boot_starter_flutter](../spring-boot-starter-flutter/optimizations.md), since the starter depends on it. |

## See also

- [Modules left out of the build](../spring-core-dart-generator/optimizations/build-conditions.md)
- [How the generation works: starter parts](../spring-core-dart-generator/how-it-works.md#starter-parts)
- [The builders](../spring-core-dart-generator/builders.md)
- [The debug tab and the log](debug-tab.md)
- [What the build checks](build-checks.md)
