A JavaScript and TypeScript inspector for busy coders.
![I'm just a placeholder!](data:image/svg+xml,%3Csvg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1440 996"%3E%3C/svg%3E)
Hypercharge your frontend workflow.
Connect to and debug your Node.js and web apps.
Write code faster with live inline values right beside your source.
Get instant feedback with in-editor scratchpads and UI plagrounds.
Insight.js is designed to work everywhere that JavaScript runs
Check out integration examples on Github..
Insight.js displays runtime values in your editor right beside your source code. Errors too!
You can use Insight.js's App Monitor to view live data from your program as it runs. It works everywhere and anywhere JavaScript runs: browsers, Node, and beyond!
Explore deeply-nested objects real-time, no need for a debugger.
Spin up a Node or web sandbox in a snap.
Works with Babel, TypeScript, Node.js, Webpack, Rollup, and much more.
Build and preview UI components without leaving VSCode.
Insight.js's UI playgrounds detect and preview your React components as you edit them.
Scrub forward and backwards through your program's execution, step-by-step.
Plus even more magic on the way. β¨
In code, binary search looks like this. And from my perspective, you can't see anything here. You can't see anything. I see the word "array" but I don't actually see an array. And so, in order to write code like this, you have to imagine an array in your head, and you essentially have to "play computer". You have to simulate in your head what each line of code would do on a computer. And to a large extent, the people that we consider to be skilled software engineers are just those people that are really good at "playing computer." But if we're writing our code on a computer, why are we simulating what a computer would do, in our head? Why doesn't the computer just do it and show us?