Debugger frontend for React Native based on Chrome DevTools
Experimental debugger shell for React Native for use with @react-native/debugger-frontend
Appium proxy for Remote Debugger protocol
A toolkit for JavaScript codemods
Files for enabling office add-in web debugging using Node and VS Code.
Debugger of the Solid's reactivity graph — a cornerstone of all solid-devtools.
Allows libraries to handle various caller provided asynchronous functions uniformly. Maps promises, observables, child processes and streams, and callbacks to callback style.
Settle an async function.
Remove debugger statements
The grunt command line interface
tab completion helpers, for node cli programs. Inspired by npm completion.
🐊Putout plugin adds ability to find and remove 'debugger' statement
Helper to use emmet modules in Visual Studio Code
JupyterLab - Debugger Extension
Debug Lambda functions locally like it is running in the cloud
JupyterLab - Debugger Extension
Replace `open debugger-ui with Chrome` to `open React Native Debugger` from react-native packager
Wireframe debugger for use with cannon-es https://github.com/pmndrs/cannon-es
CSS language support for the CodeMirror code editor
TypeScript definitions for debug
Storybook: Develop, document, and test UI components in isolation
The DevCycle Web Debugger used for debugging feature flags from your own website
TypeScript Language Service Completion API is slow when calculate auto-import.
Debugger for vite-plugin-entry-shaking
Provides debugger with command and command arguments completion, compliments of bond.
The default irb completion code shipped with ruby produces an internal error, exiting from the running script. This script makes it easy to check if a suggested patch has been applied to your current ruby version.
Debuggers are great! They help us troubleshoot complicated programming problems by inspecting values produced by code, line by line. They are invaluable when trying to understand what is going on in a large application composed of thousands or millions of lines of code. In day-to-day test-driven development and simple debugging though, a puts statement can be a lot quicker in revealing what is going on than halting execution completely just to inspect a single value or a few. This is certainly true when writing the simplest possible code that could possibly work, and running a test every few seconds or minutes. Problem is you need to locate puts statements in large output logs, know which file names, line numbers, classes, and methods contained the puts statements, find out what variable names are being printed, and see nicely formatted output. Enter puts_debuggerer. A guilt-free puts debugging Ruby gem FTW that prints file names, line numbers, class names, method names, and code statements; and formats output nicely courtesy of awesome_print. Partially inspired by this blog post: https://tenderlovemaking.com/2016/02/05/i-am-a-puts-debuggerer.html (Credit to Tenderlove.)