Skip to content

Recover when the interceptor registry appears after a slow boot - #7

Merged
pascalbaljet merged 1 commit into
masterfrom
improve-detect-timing
Jul 30, 2026
Merged

Recover when the interceptor registry appears after a slow boot#7
pascalbaljet merged 1 commit into
masterfrom
improve-detect-timing

Conversation

@pascalbaljet

Copy link
Copy Markdown
Member

The extension polled for window.__inertia_interceptors__ every 50 milliseconds, showed its "not running in dev mode" banner after one second, and stopped polling entirely after five. An app that boots later than that, left the panel showing that banner for the rest of the page's life even though Vite was running and the registry had appeared in the meantime.

The poll now backs off geometrically, from 50 milliseconds up to a five second beat that keeps running, so a late registry still attaches and flips the banner back off. The banner itself waits three seconds instead of one, and the console warning still fires once at the five second mark. On a page the recorder never stamped, the beat stops as soon as the document is parsed, so nothing keeps ticking where devtools was never enabled.

Fixes #3.

@pascalbaljet
pascalbaljet merged commit ff305f5 into master Jul 30, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Chrome extension does not recover when interceptor registry appears after the initial grace period

1 participant