What a build contains

What a build of an application with spring_boot_starter_web 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). The modules of the packages it depends on come with it: for spring_boot_dart, see Auto-configuration.

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
springBootStarterWebDebugQpsAutoConfiguration spring.web.debug.qps.enabled no build The qps debug feature: requestRateFilter counts the requests of its isolate and requestRates gives the rate of every isolate and of all together. Without the key the application has no code that counts its requests. Also native only.

By platform

platform:: the module is only in the build of that platform; no property is read.

Module Platform What it holds
springBootStarterWebAutoConfiguration native The web MVC beans (webMvcAutoConfiguration).
springBootStarterWebRateLimitAutoConfiguration native The rate limiter (spring.web.rate-limit.*, @RateLimiter), registered when it is on; it comes after the modules of the Supabase and data starters that bring a store of their own.

native: builds where dart:io exists (a server, an AOT executable, a Flutter app on a phone or a desktop), not a browser build. server: native without Flutter, never a Flutter app. -DSPRING_ALL_PLATFORMS=true keeps every module.

What the generator writes for it

A part of the generator (see Starter parts) runs only when the application reaches its package.

Part or builder What it does
Web part (spring_web_dart) Writes nothing: says which classes the build describes for the values of request mappings (@GetMapping, @PostMapping, ...) and @ExceptionHandler.

Good to know

See also