@divebell/extension-rstack

Observe Rspack HMR and React Refresh through non-pausing logpoints in the compiled JavaScript loaded by Chromium. The Extension does not require source maps and does not integrate @divebell/core into the application or @rspack/plugin-react-refresh.

Install the Rstack Extension, then open the page. The MF Extension is optional and only adds runtime ownership and shared-provider evidence:

divebell extensions add @divebell/extension-rstack
divebell open http://localhost:3000
divebell stack --refresh
divebell rstack status
divebell rstack hmr inspect

Stack detection does not install a DOM observer or enable the Debugger. After the page loads, it collects JavaScript URLs from document.scripts and Script Resource Timing entries, keeps only index*, *main*, and runtime* filenames, and fetches every distinct match sequentially with cache: "force-cache" until one contains data-rspack. Each request has a 1.2 second timeout; fetch, CORS, CSP, and response failures produce no page exception and no positive detection.

stack returns only compact Rspack detection evidence and the recommended rstack command. Run divebell rstack status for the matched script and statically recoverable official Rspack configuration. rspackConfig preserves the documented config hierarchy and may include output.publicPath and bundler information. Rspack 2 uses output.bundlerInfo; Rspack 1 uses experiments.rspackFuture.bundlerInfo, as specified by the current Rspack documentation. Runtime IDs, base URI, dynamic expressions, and generated filename functions are omitted because they cannot be mapped unambiguously to authored configuration. The fetched bundle is never executed. A missing field means only that its exact config value was not statically recoverable.

Production Rspack can be detected without HMR. HMR and React Refresh are inspected separately by rstack hmr inspect. Use stack --refresh after upgrading this Extension or when the same page URL already has a cached stack result. rstack status performs a fresh bounded inspection on each run.

Add @divebell/extension-mf and open with --mf only when Module Federation ownership or shared React evidence is needed.

Prepare the observation before changing code:

divebell rstack hmr start --expect applied --expect-refresh --expect-no-reload
# edit the source file only after status is ready
divebell rstack hmr wait <observation-id> --timeout 15000
divebell rstack hmr stop <observation-id>

hmr start returns the observationId; hmr status, hmr wait, and hmr stop may omit it when exactly one observation is active in the current project.

ready has a precise meaning: the debugger is enabled for the current CDP page session, the loaded HMR and React Refresh runtime components have been identified, the required HMR status logpoint is bound, optional Refresh/error/reload logpoints have been attempted, and the event, Console, optional page-state, and MF evidence baselines have been persisted. It does not mean that a source edit has already been detected. The result also returns nextAction: "change-source"; make the edit only after this result.

The report keeps the HMR runtime, React Refresh runtime, changed module owner, and MF shared React provider as separate evidence. Shared react and react-dom traces are collected independently for every current MF consumer or mixed runtime instance.

inspect reports React Fast Refresh preconditions in this order:

1. loaded ReactDOM build (development, production, or ambiguous);
2. whether globalThis.__REACT_DEVTOOLS_GLOBAL_HOOK__ is installed;
3. registered renderer build and the scheduleRefresh / setRefreshHandler helpers.

Its discovery output keeps hmrRuntimes and reactRefreshRuntimes separate. The first list contains Rspack HMR state machines; the second contains React Refresh adapters, even when both components are compiled into the same file. probePlans are candidate non-pausing logpoint locations and are not installed until start. Each plan includes runtimeKind and runtimeId so it can be associated with the corresponding runtime list. By default, start groups readiness under rspackHmr and reactRefresh. Use start --verbose to read the Refresh preflight and installed probe count.

Run divebell rstack --skill for the full field semantics and decision rules for rstack status and the rstack hmr workflow.

start --expect-refresh fails before becoming ready when no compatible development ReactDOM renderer is ready. This does not block plain Rspack HMR observation.

Page reload and module HMR are separate outcomes. After an apply-to-idle path, wait keeps observing for a short settle window. A main-document commit during that window produces rspackHmr.outcome: "reloaded"; it cannot pass as applied HMR. rspackHmr.sameDocument reports whether the observed update stayed in the same document.

hmr status and hmr wait return compact results with independent rspackHmr, reactRefresh, and ui sections. expectations.verdict grades only the expectations selected by start; it is not an overall UI success claim. An applied Rspack cycle can coexist with reactRefresh.outcome: "not-completed". Use --verbose for full runtimes, cycles, preflight, page reload, MF shared, probe, and event evidence under details and evidence.

Use wait with --expect applied for a pass/fail answer. On failure, rerun status <observation-id> --verbose to inspect the runtime-scoped status path, module IDs, compiled locations, probe gaps, Refresh boundary branch, reload evidence, and MF owner/provider evidence. Compilation failures are explicitly reported as Console fallback evidence because no build-server integration is required.