| I subscribe to all three products from the Wallaby team. - Console Ninja. Inspect runtime values on any line of TS/JS code by putting breakpoints on the source. Inspect values, errors, and stacktraces next to their corresponding lines without leaving VSCode/Cursor. This works well with frontend or backend TS/JS, so in a NextJS app I can inspect anything without leaving the editor. No more checking console logs in Chrome dev tools. I found this tool invaluable when I switched to React and wanted insight into what data the components contained between renders. Also has a MCP server so Cursor can have access to all these runtime values and errors too. https://console-ninja.com/ - WallabyJS. Similar, but a test runner that runs tests as you type, and can display values and test failures inline. Also with a MCP server to give tools like Cursor feedback on runtime values and test failures inline data for quick iterations. https://wallabyjs.com/blog/wallaby-mcp.html - Quokka. Similar concept, but a TS/JS playground for prototyping code. Can temporarily install and later discard NPM dependencies for trying out libraries. Snaps allow fenced blocks of prototype code to be immediately evaluated inside existing codebases, then discarded when not needed. https://quokkajs.com/ I think Console Ninja and Quokka also have free versions with some Pro features missing. Those who have been around here for a while might remember Bret Victor presentations and the kickstarter for the LightTable IDE. To me, the Wallaby tools are effectively that. Runtime insight, inline as you develop. |