What nanostores-devtools draws, and why it draws it that way. Getting started covers install and setup, and the API page has every option’s name and default. This section explains how a store gets its name, where it lands in the tree, what a timeline row means, what a value shows, and what the package cannot do.
Every rule and edge case behind these pages, for anyone changing the package, is in REFERENCE.md. How the code itself is put together is in ARCHITECTURE.md.
How stores get in
The bundler plugin and trackStores, and the reachability rule that decides which stores the plugin draws.
The state tree
Homes, owners, (value), the kind in square brackets, how a tree key is built, and what happens when two stores share a name.
The timeline
Every row name, when stores join and leave, and why a hot reload draws one row instead of a pair.
connectDevtools options
What each bridge option buys you and what it costs, plus the four comments the plugin reads and the serializers.
Plugin options
maxDepth, storeTypes, fileKey and projectRoot, and what parsing every file costs.
Production builds
The production export condition, bundler by bundler, and the explicit pattern for anyone who wants control.
Troubleshooting
What to check when the panel shows nothing, or less than you expected.