A dead-simple way to configure submodules. They locate your toplevel package.json's config section, or otherwise named json file, and derive their config values from there. It's a read-only config, and the recommended use is that you just store your confi
Configuration file loader for @rushstack/heft
Extract the non-magic parent path from a glob string.
Get the path of the parent module
Utility function to load nyc configuration
Adds a static `extend` method to a class, to simplify inheritance. Extends the static properties, prototype properties, and descriptors from a `Parent` constructor onto `Child` constructors.
Configuration management for the npm cli
Find the first config file matching a given name in the current directory or the nearest ancestor directory.
Standard shareable config for Stylelint
EditorConfig File Locator and Interpreter for Node.js
Resolve a path by walking parent directories.
Run a child as if it's the foreground process. Give it stdio. Exit when it exits.
Finds the first parent directory that contains a given file or directory.
A JS implementation of JSONPath with some additional operators
Traverse JSON Schema passing each schema object to callback
Resolve things like Node.js — ponyfill for `import.meta.resolve`
Require modules from parent modules.
Library to walk OAS 3 schema objects and call a callback
Check that two PostCSS nodes share the same parent.
Markdown language support for the CodeMirror code editor
HTML language support for the CodeMirror code editor
A library for one-to-many cross-origin communication between Window contexts, built on the postMessage API.
Keep iframes sized to their content.
Get all children of a pid
Test Kitchen Parent-Child is a thin wrapper around Test Kitchen that adds support for inheritance in the .kitchen.yml configuration files for multi-role projects.
If you are a guy who always find something wrong only after sending a pull requset, Priha will help you because Priha lets you examine files' diff between the parent branch and HEAD of the current branch in a real GitHub pull request. However, DO NOT use Priha for your secret repostitory. Since Priha pushes some commits to another repository on GitHub, it easily cause a security incident, espacially the branch you set for Priha is "public". Also, Priha removes all branches on the repository specified in config, so you MUST create a new repository for this purpose and DO NOT use the existing one.
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.