React integration for Retil sources
Use source maps on the server to generate readable browser stack traces
Don't use this package from npm instead feel free to fork or use source code directly.
Use source maps to trace back the sources that contribute to your minified JavaScript artifact.
Creates a pair of source and sink
Use source-map-explorer to generate a visual representation of your source maps with rollup
A utility to use source maps to convert a minified stack trace into something human readable
Use source maps on the server to generate readable browser stack traces
Um pacote para gerenciamento de dados para requisiçoes http.
Generates and consumes source maps
Vite plugin for monorepo - auto-discover local packages and use source code in browser
CLI tool for monorepo - auto-discover local packages and use source code in Node.js
Generates and consumes source maps
CLI tool for monorepo - auto-discover local packages and use source code in Node.js
A React helper hook for scheduling a layout effect with a fallback to a regular effect for environments where layout effects should not be used (such as server-side rendering).
Check if a character is hexadecimal
Check if a character is alphanumerical
Count how often a character (or substring) is used in a string
Check if a character is decimal
Check if a character is alphabetical
Decode named character references
Generate a markdown (GFM) table
Download and launch browsers
Throw a given error
Open-source Dropbox using Ruby and Git.
Event sourcing toolkit using Rails and ActiveJob
A reusable rake task to vendorise a gem hosted in a private git repo
Ruby bindings for IMDb using imdbapi.com as source
Add the 'gitian' sub-commands to the gem command
A set of useful stuff for event sourcing.
A Jekyll plugin that converts the AsciiDoc source files in your site to HTML pages using Asciidoctor.
Source code parser used internally by jievro
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.)
Using current sources for your pods.
Track Kanban metrics using Asana as a data source
Open Source software build descriptions for use with Omnibus
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.