fx printed its dependency graph and its start and stop hooks through
its console logger on standard error. fx.WithLogger now hands those
events to the service's logger: building the graph at DEBUG, the hooks,
the start and the stopping signal at INFO, failures at ERROR. The fx
logger's constructor takes the configuration, so the level DEBUG=true
sets is in force before fx replays the events it held back; a failure
before that, such as an invalid configuration value, still goes to
fx's console logger. FxLogger in internal/logger holds one SlogLogger
per level. fx moves from v1.20.1, which has no SlogLogger, to v1.24.0.
The README names the Go runtime and that early failure as writers
outside internal/logger.
Model: opus-5-5
sneak