René's URL Explorer Experiment


Title: Inspectro: See the invisible

Open Graph Title: Inspectro: See the invisible

X Title: Inspectro: See the invisible

Description: The runtime DevTools platform for VS Code. Inspect your component tree, renders, network and SSR execution -- the runtime your browser hides and your AI can't watch -- one click from your editor.

Open Graph Description: The runtime DevTools platform for VS Code. See your components, renders, network and SSR execution (the runtime your browser hides and your AI can't watch) in one place, one click from your editor.

X Description: The runtime DevTools platform for VS Code. See your components, renders, network and SSR execution (the runtime your browser hides and your AI can't watch) in one place, one click from your editor.

direct link

Domain: inspectro.dev


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"FAQPage","url":"https://inspectro.dev","mainEntity":[{"@type":"Question","name":"What is Inspectro?","acceptedAnswer":{"@type":"Answer","text":"A VS Code extension that makes your running frontend inspectable from inside the editor. It attaches to the dev server you already run and gives you a component tree with click-to-source, plus network, performance, coverage, console, cookies, a real debugger and a live preview. The DevTools UI itself opens in your browser, one click from the editor, and every component in it opens its source back in VS Code."}},{"@type":"Question","name":"How is this different from my browser's DevTools?","acceptedAnswer":{"@type":"Answer","text":"Two things your browser can't do. Components in the tree open the file that rendered them, in your editor. And it can pause your server-side code: the Debug tab attaches to the dev server's own Node process, so a breakpoint fires during SSR, before the HTML is ever sent. The inspectro.debug.runtime setting picks node for server code, browser for client code, or dual for both."}},{"@type":"Question","name":"Can I switch environments, or sign in as a real user?","acceptedAnswer":{"@type":"Answer","text":"Yes. Both live in the Cookies tab. The environment switcher lists the environments it finds in your project; with no config it discovers your .env.* files, and environments whose file is missing are listed but disabled, so you can see which ones you don't have. Picking one restarts your dev server with that file's variables. Your DevTools session and Preview stay connected throughout, and re-point themselves the moment the new server is listening. Signing in as a user is a separate flow: give it a token endpoint, and the extension fetches the token in the editor process, hands it to the agent to set a cookie on localhost, restarts the app under that environment, and reloads the preview, showing you each step as it runs."}},{"@type":"Question","name":"Do I have to change my code or my build?","acceptedAnswer":{"@type":"Answer","text":"No. Inspectro proxies the dev server you already run and injects its agent into the HTML that server sends. There is no package to add to your project, no config file to write and no build step to start."}},{"@type":"Question","name":"Which frameworks does it work with?","acceptedAnswer":{"@type":"Answer","text":"Four: React 18+, Next.js (App and Pages Router), Angular 17+ and Vue 3 (including Nuxt 4). That is where 2025 frontend work is, by usage share: React 44.7%, Next.js 20.8%, Angular 18.2%, Vue.js 17.6%. Note that Vite and webpack are build tools, not frameworks, so they are not on that list at all: Inspectro proxies whatever dev server you run, and the framework you wrote the app in is what decides which component tree you get. The docs carry the caveats per framework."}},{"@type":"Question","name":"What do I need to run it?","acceptedAnswer":{"@type":"Answer","text":"VS Code 1.85 or newer with your project open as the workspace folder, your dev server running a development build, and a Chromium-based browser for the Preview and Debug panels. Production builds aren't inspectable in any framework: component names, source paths and props come from metadata frameworks only emit in dev."}},{"@type":"Question","name":"Does my code leave my machine?","acceptedAnswer":{"@type":"Answer","text":"The inspection is local: the agent in your app talks to the extension over a WebSocket on your own machine, against your own dev server. The only thing sent anywhere is anonymous usage analytics, which also respect VS Code's global telemetry setting, and switch off entirely with inspectro.telemetry.enabled. No source code, file contents, URLs or cookie values are ever collected. Holding an Inspectro account is separate, and the Privacy Policy sets out exactly what that stores."}},{"@type":"Question","name":"What does it cost?","acceptedAnswer":{"@type":"Answer","text":"It's free while Inspectro is in early access: the full extension, no card. Pricing after that isn't decided yet. If paid tiers do arrive, founding users hear first and the plan goes up on the pricing page before anything changes."}},{"@type":"Question","name":"When can I install it?","acceptedAnswer":{"@type":"Answer","text":"Right now — Inspectro is published on the VS Code Marketplace. Search for Inspectro in the Extensions view, or run ext install hemasai.inspectro from Quick Open."}}]}

og:site_nameInspectro
og:localeen_US
og:imagehttps://inspectro.dev/og.png
og:image:width1200
og:image:height630
og:typewebsite
twitter:cardsummary_large_image
twitter:imagehttps://inspectro.dev/og.png
twitter:image:width1200
twitter:image:height630

Links:

https://inspectro.dev/
Platformhttps://inspectro.dev/
Featureshttps://inspectro.dev/features
Docshttps://inspectro.dev/docs
Bloghttps://inspectro.dev/blog
Consultinghttps://inspectro.dev/consulting
Pricinghttps://inspectro.dev/pricing
Abouthttps://inspectro.dev/about
https://x.com/intent/post?text=Inspectro%20makes%20your%20frontend's%20runtime%20(components%2C%20renders%2C%20network%2C%20SSR)%20fully%20inspectable%20without%20ever%20leaving%20VS%20Code.&url=https%3A%2F%2Finspectro.dev
https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Finspectro.dev
Start for Freehttps://inspectro.dev/auth?mode=signup
Explore the DevToolhttps://inspectro.dev/features
Version 1.0.3 islive on the VS Code Marketplacehttps://marketplace.visualstudio.com/items?itemName=hemasai.inspectro
01InspectorComponent tree, live prop editing, click-to-source.View in Features →https://inspectro.dev/features#inspector
02NetworkEvery request, response and timing event, recorded continuously.View in Features →https://inspectro.dev/features#network
03PerformanceRender counts, timings and the context that triggered them.View in Features →https://inspectro.dev/features#performance
04Cookies & EnvironmentsFull cookie control in the panel; env & user switching is on the roadmap.View in Features →https://inspectro.dev/features#cookies
05AccessibilityAudits as a first-class engineering workflow, not a checkbox.View in Features →https://inspectro.dev/features#accessibility
06Code CoverageLine, branch and function coverage beside your source.View in Features →https://inspectro.dev/features#coverage
07DebugStep through SSR and Node over CDP: the runtime no browser shows. Client debug in beta.View in Features →https://inspectro.dev/features#debug
08PreviewLive preview with ancestry, device toolbar and paint overlays.View in Features →https://inspectro.dev/features#preview
Create your free accounthttps://inspectro.dev/auth?mode=signup
Also live on the VS Code Marketplacehttps://marketplace.visualstudio.com/items?itemName=hemasai.inspectro
The docs have a troubleshooting sectionhttps://inspectro.dev/docs#faq
Platformhttps://inspectro.dev/
Featureshttps://inspectro.dev/features
Docshttps://inspectro.dev/docs
Bloghttps://inspectro.dev/blog
Pricinghttps://inspectro.dev/pricing
Getting Startedhttps://inspectro.dev/docs#getting-started
Installationhttps://inspectro.dev/docs#installation
Commands & Settingshttps://inspectro.dev/docs#commands
Changeloghttps://inspectro.dev/docs/changelog
Abouthttps://inspectro.dev/about
Contacthttps://inspectro.dev/contact
Privacyhttps://inspectro.dev/privacy
Termshttps://inspectro.dev/terms

Viewport: width=device-width, initial-scale=1


URLs of crawlers that visited me.