Open Source TypeScript Debuggers for Windows

Flipper is a platform for debugging iOS, Android and React Native apps. Visualize, inspect, and control your apps from a simple desktop interface. Use Flipper as is or extend it using the plugin API. Flipper aims to be your number one companion for mobile app development on iOS and Android. Therefore, we provide a bunch of useful tools including a log viewer, interactive layout inspector, and network inspector. Flipper is built as a platform. In addition to using the tools already included, you can create your own plugins to visualize and debug data from your mobile apps. Flipper takes care of sending data back and forth, calling functions, and listening for events on the mobile app. Both Flipper's desktop app and native mobile SDKs are open-source and MIT licensed. This enables you to see and understand how we are building plugins, and of course join the community and help improve Flipper. We are excited to see what you will build on this platform.

Bot Framework Emulator is a desktop application that allows bot developers to test and debug bots, either locally or remotely. Using the Emulator, you can chat with your bot and inspect the messages that your bot sends and receives. The Emulator displays messages as they would appear in a web chat UI and logs JSON requests and responses as you exchange messages with your bot. Before you deploy your bot to the cloud, run it locally and test it using the Emulator. You can test your bot using the Emulator even if you haven't yet created it with Azure Bot Service or configured it to run on any channels. Before connecting your bot to the Bot Framework Emulator, you need to run your bot locally. You can use Visual Studio or Visual Studio Code to run your bot, or use the command line. When you are developing behind a corporate proxy, the Emulator will use the configured environment variables HTTP_PROXY and HTTPS_PROXY, which specify the proxy URL route for HTTP and HTTPs requests.

Browser-based frontend to gdb (gnu debugger). Add breakpoints, view the stack, visualize data structures, and more in C, C++, Go, Rust, and Fortran. Run gdbgui from the terminal and a new tab will open in your browser. gdbgui is a browser-based frontend to gdb, the gnu debugger. You can add breakpoints, view stack traces, and more in C, C++, Go, and Rust! It's perfect for beginners and experts. Simply run gdbgui from the terminal to start the gdbgui server, and a new tab will open in your browser. gdbgui is used by thousands of developers around the world including engineers at Google and college computer science course instructions. It even made its way into the Rust programming language's source code and appeared on episode 110 of C++ Weekly.

LightProxy is a local proxy packet capture software based on whistle. Packet capture, including wireless scene capture. Real-time hosts binding. Forward resources according to rules. Mock interface, page, etc. Modify the content of the request and response, for example, insert script in the page, modify the return header, etc. Start LightProxy in the application list. The first time you start LightProxy, you will be asked for the password twice. This is used to install auxiliary programs and automatically install certificates. We will complete a JSON rule through snippet, and we can quickly jump through Tab. The usage of ES6-like strings here is a grammar extended on the basis of whistle, which can support multiple lines of content written directly into the rules.

TraceRoot.AI is an open source, AI-native observability and debugging platform designed to help engineering teams resolve production issues faster. It consolidates telemetry into a single correlated execution tree that provides causal context for failures. AI agents operate over this structured view to summarize issues, pinpoint likely root causes, and even suggest actionable fixes or draft GitHub issues and pull requests. It offers interactive trace exploration with zoomable log clusters, span and latency views, and code-linked insights. Lightweight SDKs for Python and TypeScript enable seamless instrumentation using OpenTelemetry, with support for both self-hosted and cloud deployment. Human-in-the-loop interaction is central: developers can guide reasoning by selecting relevant spans or logs, then verify agent reasoning through traceable context.

Foxglove Studio is an open-source visualization and debugging tool for robotics. Use customizable layouts to arrange interactive visualizations and quickly understand what your robot is doing. Use Foxglove Studio's rich interactive visualizations to analyze live connections and pre-recorded data. Experience the world as your robot does. Visualize images and point clouds, overlay bounding boxes, add classification labels and planned movements, and drill down into your data with plots or raw message views. Upload recordings to your private data lake for easy storage, searching, and analysis. Stream recorded data directly into Foxglove Studio to get insights into your robots' behavior. We're long-time fans and beneficiaries of open source software. Join our community on Github and Slack to contribute bug reports, feature requests, or pull requests.

Browser Preview for VS Code enables you to open a real browser preview inside your editor that you can debug. Browser Preview is powered by headless Chromium, and works by starting a headless Chromium instance in a new process. This can either be Google Chrome or Microsoft Edge. This enables a secure way to render web content inside VS Code, and enables interesting features such as in-editor debugging and more! Make sure you have Google Chrome installed on your computer. Browser Preview for VS Code is debuggable, launch URLs and attach Debugger for Chrome to the browser view instance, and debug within VS Code. You can enable in-editor debugging of Browser Preview by installing Debugger for Chrome, and configure VS Code's debugger to either attach or launch to the browser previews by using the provided configuration options.

A VS Code extension to debug your JavaScript code in the Google Chrome browser, or other targets that support the Chrome DevTools Protocol. When your launch config is set up, you can debug your project. Pick a launch config from the dropdown on the Debug pane in Code. Press the play button or F5 to start. The extension operates in two modes - it can launch an instance of Chrome navigated to your app, or it can attach to a running instance of Chrome. Both modes require you to be serving your web application from a local web server, which is started from either a VS Code task or from your command line. Using the URL parameter you simply tell VS Code which URL to either open or launch in Chrome. Just like when using the Node debugger, you configure these modes with a .vscode/launch.json file in the root directory of your project. You can create this file manually, or Code will create one for you if you try to run your project, and it doesn't exist yet.