
# What a build contains

What a build of an application with `spring_boot_starter_edge` 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 |
|---|---|
| `springBootStarterEdgeAutoConfiguration` | The fetch server of a function and the runtime, before the web starter's module. In a Supabase Edge Function it also gives `spring.supabase.url`, `spring.supabase.anon-key` and `spring.supabase.service-role-key` the values of the function's environment, below everything the application sets itself. |

## 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 |
|---|---|---|---|
| `springBootStarterEdgeStartupChecksAutoConfiguration` | `spring.main.startup-checks.enabled` | debug and profile builds only | `edgeWarnings` and its `EdgeWarningContributor` beans: in a function, the list of what works differently there, logged once at the start. `spring.edge.warnings: false` turns it off where the module is in the build. |

## 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 |
|---|---|
| Through its dependencies | No part of its own. The web part runs, since the starter depends on `spring_web_dart`. |

## Good to know

- A function compiled by `dart compile js` or `wasm` is not a release build in this sense (it defines no `dart.vm.product`), so it keeps the warning list unless the key is `false`.
- `dart run spring_boot_starter_edge:build` compiles with `-DSPRING_ALL_PLATFORMS=true`, so the modules of the application's other starters that are for `native` or `server` only stay in a function.

## 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)
- [Building](building.md)
- [What a function does differently](differences.md)
