liveBook · Manning

Code reloading

Code reloading is a development technique that detects changed code or resources and refreshes, reevaluates, or restarts affected application components without requiring a full manual restart.

How 4 Manning books explain it

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

A development technique that detects source-code changes and automatically restarts or reloads a running application.

How it is used
Shortens development feedback by restarting changed microservices automatically instead of requiring manual restarts or repeated application rebuilds.
How deep it goes
Works through nodemon installation, npm scripts, container code sharing, a reload check, and a file-watching workaround.
Examples
Uses a startup-message edit in a Compose application and Jest commands that rerun tests after code changes.
What you can do after
Operate/configure it with nodemon and Docker Compose so edited microservices restart, and use Jest watch mode for test feedback.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains code reloading →

Quarkus in Action

A development-time process that applies code or configuration changes by reloading an application without a full manual restart.

How it is used
Shortens the Quarkus development edit–check loop by applying saved changes when the running application receives a request.
How deep it goes
Explains triggers, request handling, state loss, and optional instrumentation, but defers class-loader architecture details.
Examples
Uses a changed REST greeting, a missing semicolon, and Dev mode console logs to demonstrate successful and failed reloads.
What you can do after
Operate/configure it with Quarkus Dev mode commands, request-triggered reloads, and the optional instrumentation setting.

Read how Quarkus in Action explains code reloading →

Pro Angular 16

Hot reload is a development technique that updates a running application after source changes without requiring a full restart.

How it is used
Provides automatic browser feedback after saved source changes during Angular development.
How deep it goes
Explains change detection, selective bundle rebuilding, and the server signal that reloads the browser; does not describe preserving page state.
Examples
Uses `main.ts` console messages and an `app.component.html` template edit, with browser output and a build report.
What you can do after
Operate/configure it by running `ng serve`, saving an edit, and checking the browser or build output for the result.

Read how Pro Angular 16 explains code reloading →

.NET MAUI in Action

Hot reload on file save is an automatic hot-reload mode that applies supported changes when a source file is saved.

How it is used
Accelerates the inner development loop for .NET MAUI apps by showing supported edits while the app continues running.
How deep it goes
Explains file-save activation, supported edits, and rebuild limits caused by immutable CLR metadata and resources.
Examples
Uses greeting edits, XAML layout changes, and a custom Dotnet Bot image to contrast reloadable and rebuild-required changes.
What you can do after
Apply it via Visual Studio to iterate on running .NET MAUI interfaces without restarting after every supported edit.

Read how .NET MAUI in Action explains code reloading →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.