A library for parsing VS Code style problem matchers
Allows you to build compile-time libraries
Frequent default values
A drop-in replacement / proxy to Node.js path, replacing \\ with / for all results & adding file extension functions.
A React component that allow to bind events on the global scope
Run scripts that set and use environment variables across platforms
pipe streams together and close all of them if one of them closes
Info about your dev environment for debugging purposes
Lexes CommonJS modules, returning their named exports metadata
Removes React properties
Parse, Resolve, and Dereference JSON Schema $ref pointers
Ship compositional knowledge for AI coding agents alongside your npm packages
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
A bcrypt library for NodeJS.
Stop your iOS webapp from bouncing around when scrolling
A fast linked list (good for queues, stacks, etc.)
Strongly-typed string functions.
A Node.js style checker and lint tool for Markdown/CommonMark files.
Additional Jest matchers
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
A list of all the problem landlords in Chicago and their location, as PORO. No messing with JSON required!
This gem is the solution to the conference talks problem
== FEATURES/PROBLEMS: * FIX (list of features or problems) == SYNOPSIS: Use mongrel_appcast, like the mongrel_rails command. == REQUIREMENTS:
== FEATURES/PROBLEMS: * FIX (list of features or problems) == SYNOPSIS: FIX (code sample of usage) == REQUIREMENTS:
== FEATURES/PROBLEMS: * FIX (list of features or problems) == SYNOPSIS: FIX (code sample of usage) == REQUIREMENTS:
gem-status gets the list of gems you use from Gemfile.lock file and runs some checks on those gems. Checks that can be run are: * Does it has a license? If it does not, it can be a problem for distributing your software with this gem. * Is it Gpl? If it is, it can be a problem if your software or other gems are not GPL compatible. * Is the same in Rubygems.org? This is for people who uses his own gem server. This checks the gems are the same. * Does it has security alerts? This will search into the commits and into security mailing lists for possible security messages.
Outputs a list of bits of code which should be reviewed as they could potentialy lead to later problem from current code changes
Based on memcache-client by <a href="http://dev.robotcoop.com/">robotcoop</a>. We started out with their code, but ended up with an almost complete rewrite after having added code for our own needs and requirements. Apologies for not doing proper contributions to their project instead of building our own, but we are limited by commercial requirements rather than open source idealism. == FEATURES/PROBLEMS: * FIX (list of features or problems) == SYNOPSYS:
== FEATURES/PROBLEMS: * List bundles available in the Macromates repository * Install, uninstall and update bundles * Install bundles from third-party repositories * Automatic reloading of TextMate bundles. == SYNOPSIS: Run 'bundlemate help' for instructions. == REQUIREMENTS:
Nicolus is a simple program to make all possible combination out of 2 or more lists of words. == FEATURES/PROBLEMS: * Command line parser * "inverse" generate "aaa 111" and "111 aaa" == SYNOPSIS:
A regression testing tool ensure that new problems and unexpected behaviors will not be introduced to PMD project after fixing an issue and new rules work as expected. == Features/Problems: The diff report can be generated according to the base and patch branch of PMD on a list of standard projects (e.g. Spring Framework, Checkstyle, OpenJDK, etc.). Rule violations and code duplications are compared to report, which are new, removed or changed. While executing PMD, JDK Flight Recorder (jfr) is enabled and a recording is created. This allows to investigate performance and memory issues afterwards.
There is a problem with fron-end testing. Websites are always changing. **Zander** audaciously attempts to provid a solution. Give zander two files `sites.yaml` and `actions.yaml`, and it will do all the work. `sites.yaml` will hold a list of URLs and any variables like user_name or password that are assocaited to a URL. `actions.yaml` is a list of actions to take. actions contain attributes like action_type and identifier where you specify the action to preform and how to identifie the DOM element. See Custom Input Example below.
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.