Internals

The internals section explains how next.dj works under the hood. Each page traces one pipeline with a mermaid diagram, lists the modules involved, and points at the public hooks used to extend it. The pages read top to bottom, from a whole-framework map down to individual subsystem pipelines. The partial rendering pipeline is traced in How a partial request flows rather than on a page here.

Internals overview

Map of every subsystem with a signals fan-out diagram.

Request lifecycle

End to end path of an HTTP request.

Page discovery

Page modules, layouts, context.

URL router

URL parsing, dispatch, reload.

Component pipeline

Component discovery, loading, rendering.

Dependency resolver

Parameter resolution, providers, cache.

Static pipeline

Asset discovery, collector, backends, injection.

Action dispatch

Form dispatch, validation, re-render.

Autoreload

Watchers, route reload, signals.

Contributor notes

Conventions the framework code follows.