Changelog

Starting a new dev-server session now clears stale authentication state, so a previous project's sign-in cannot carry into the next session.

• FIXA new Inspectro session now invalidates the previous WebSocket connection, session token, and environment-auth state. When fresh cookies are enabled, stale browser cookies are cleared too, preventing one project's sign-in from carrying into another.

The Debug tab's editor now works like VS Code's. It loads only when you first open the Debug tab, so the other tabs are not slowed down. If it cannot load, the Debug tab falls back to the plain editor it had before, and editing and saving still work.

• NEWThe Debug tab's editor runs on Monaco, the editor VS Code is built on, and every answer comes from VS Code's own language services for your project — the same TypeScript, the same settings, the same results you see in the editor: errors and warnings underlined as you type, matching the Problems panel; completion, including TypeScript's auto-import, so accepting a suggestion adds its import line for you; hover types and docs, and signature help while you type arguments; go to definition (F12), find references (Shift+F12) and rename (F2) across files.
• NEWOne file, one buffer. The Debug tab edits the same document VS Code has open. Type on either side and it appears on the other at once, with VS Code's unsaved dot; save from either side and both clear. No "file changed on disk" prompts.
• NEWKeep editing while paused. The editor stays writable at a breakpoint, as it does in VS Code.
• NEWHide the file explorer with the new toolbar button or Cmd+B / Ctrl+B, and the editor takes the full width. Your choice is remembered.
• FIXOpening a second file from the Debug tab now switches to it. Previously the file opened but the tab you were on stayed selected.

Listing and settings corrections. No functional change — the extension itself behaves exactly as 1.0.0 did, so there is nothing to re-learn.

• FIXThe description no longer claims the DevTools run inside VS Code. They do not, and never did: Inspectro opens its DevTools UI in your browser and wires it back to the editor, which is the whole reason it can inspect a live app. The Marketplace description, the README heading and the 1.0.0 notes all said otherwise. That was our error, and it set the wrong expectation before anyone had installed anything.
• FIXGetting Started now says an account is required. Sign-in gates Open DevTools and Run Dev Server, and the old steps walked you to a dead end without mentioning it.
• FIXThe deeper inspection menu is Ctrl+right-click, not Alt+right-click. The README had the wrong modifier.
• FIXThe second screenshot is SSR debugging, not debug paint. Caption and image now agree.
• FIXWhat Inspectro writes to your project is stated plainly. The environment switcher creates inspectro.env.json and a self-ignoring .inspectro/ folder, and both survive an uninstall. The old wording said nothing is written and that removing the extension removes everything.
• FIXThe License section names the licence. Inspectro is proprietary, commercially licensed software, with the full terms at inspectro.dev/terms.
• IMPRemoved three settings that were declared in the manifest but never read by any code: inspectro.autoStart, inspectro.editor and inspectro.debugPaintDefault. They appeared in the Settings UI, accepted values, and did nothing. Nothing changes by removing them, because nothing changed by setting them — but VS Code may flag them as unknown if you had set one, in which case delete the line from your settings.json.

First public release. Inspectro attaches to your running React, Next.js, Angular or Vue app and brings component-level DevTools to your browser, wired to VS Code — plus SSR debugging the browser cannot do on its own.

• NEWComponent tree with click-to-source. Select a node to open its file; select in the browser to reveal it in the tree.
• NEWHover inspector. Point at any element for its tag, size, colour, font, spacing and accessibility, alongside what the framework knows about it: the component's source file and line, its props, which props just changed, its state, and its event handlers. React state is labelled with your own variable names, read from your source.
• NEWDebug paint. Every component the framework owns, outlined and measured.
• NEWLayout inspector — the box model with live computed values.
• NEWLive prop editing for strings, numbers and booleans, applied immediately.
• NEWAccessibility dashboard — contrast, alt text, ARIA, labels, heading order, scored and pushed to VS Code's Problems panel.
• NEWPerformance profiling — render counts, timings and wasted renders.
• NEWNetwork inspector — every fetch and XMLHttpRequest with bodies and timing.
• NEWCode coverage — Istanbul, LCOV and Cobertura reports, per file and folder.
• NEWCookies, console and an embedded preview, all in the same panel.
• NEWSSR debugging. Real breakpoints in server-side code over the Node inspect port, which browser DevTools cannot reach.
• FIXValues are current, not one render behind. React keeps two fibers per component and caches one on the DOM node at mount, so after a re-render the cached one belongs to the old tree — every prop and state value the extension displayed could be a render stale. It now always reads the live tree.
• FIXuseMemo, useRef and useEffect are no longer counted as state. A component with three useState calls reported five values.
• FIXState and changed-prop detection work on all four frameworks. Both were React-only in places; Angular reported no state at all, and the Inspector panel hid changed-prop data it was already being sent.
• FIXThe inspector no longer attributes a component's props to elements it merely contains. Hovering an h1 inside a component showed that component's props as though they belonged to the heading.
• FIXOverlays no longer linger on the page you just left. Navigating could leave outlines and a label floating over the new page for a second or more.
• FIXAccessibility reporting corrected. A paragraph reported its ARIA role as generic rather than paragraph, and claimed an accessible name that screen readers would never announce.
• FIXStyle edits from the Styles pane rewrite the class rather than stamping an inline style, no longer flicker back to the old value after saving, and no longer blank the pane on hot reload.
• FIXAngular live prop edits reach the screen. Angular 17+ props are signals and were being overwritten with raw values, breaking the next change-detection pass.
• FIXLight and dark themes both meet WCAG AA. Dim text failed the 4.5:1 floor on every surface in dark and on raised surfaces in light; button text on coloured fills rendered black in the light theme.
• NEWSecurity: the WebSocket server binds to 127.0.0.1, requires the current session's token, and accepts only local origins.
• NEWSecurity: telemetry is anonymous and opt-out. It respects VS Code's global telemetry setting and inspectro.telemetry.enabled, and is filtered by an allow-list at its single exit point, so a file path, component name or prop value cannot be sent even by accident.
• NEWSecurity: your source is read and edited locally through VS Code. Nothing about your components, props, paths or network payloads leaves your machine.

On the version number: Inspectro reached 2.4.0 as an internal build before it was ever published. The first public release is 1.0.0, per semver's rule that 1.0.0 is the first stable public API. Those pre-release builds were never distributed, so their history is not reproduced here.