Solves the halting problem :)
A utility for checking a specific version of the halting problem in Node.js code.
Add sleep() and usleep() to nodejs
A library for parsing VS Code style problem matchers
Allows you to build compile-time libraries
A drop-in replacement / proxy to Node.js path, replacing \\ with / for all results & adding file extension functions.
Run scripts that set and use environment variables across platforms
Muxified Turing Machine
pipe streams together and close all of them if one of them closes
Info about your dev environment for debugging purposes
Parse, Resolve, and Dereference JSON Schema $ref pointers
A trailing node plugin for the prosemirror editor.
Right To Left conversion for CSS in JS objects
Type safe utilities for throwing errors (and responses) if things aren't quite right. Inspired by npm.im/invariant
Additional Jest matchers
Strongly-typed string functions.
Simple and complete React Native testing utilities that encourage good testing practices.
common library for micromark-extension-cjk-friendly and its related packages
stand-alone library of threejs examples
remark plugin to make Markdown strikethrough (`~~`) in GFM more friendly with Chinese, Japanese, and Korean (CJK)
micromark extension to make Markdown strikethrough (`~~`) in GFM more friendly with Chinese, Japanese, and Korean (CJK)
The NetBSD AMD64 binary for esbuild, a JavaScript bundler.
AsyncAPI Problem interface
Parse, Resolve, and Dereference JSON Schema $ref pointers
An RSpec matcher that solves the halting problem
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.)