Creates a function that handles commands in a reSolve application.
resolve like require.resolve() on behalf of files asynchronously and synchronously
Locate and bundle third-party dependencies in node_modules
Offers a async require.resolve function. It's highly configurable.
A deep deletion module for node (like `rm -rf`)
Resolve a URI relative to an optional base URI
Resolve a relative path against a root path with validation
Universal module importer for Node.js
Resolve things like Node.js — ponyfill for `import.meta.resolve`
TypeScript definitions for resolve
Resolve the path of a module like `require.resolve()` but from a given path
micromark utility to resolve subtokens
Resolve a directory that is either local, global or in the user's home directory.
Resolve package.json exports & imports maps
Resolve URL pathnames using JavaScript
Resolve the path of a module like `require.resolve()` but from the current working directory
A fork of `import-meta-resolve` with commonjs + ESM support at the same time, AKA dual package.
Missing ECMAScript module utils for Node.js
Resolve nested CSS selectors
Resolve a nested selector in a PostCSS AST
Module resolution utilities based on Node.js upstream implementation.
Detects the ALPN protocol
Convert CommonJS modules to ES2015
Babel plugin for resolving Vue types.
Resolve dependencies, merge and minify CSS and JavaScript files with Juicer - the command line tool for frontend engineers
Resolve dependencies, merge and minify CSS and JavaScript files with Juicer - the command line tool for frontend engineers
Another Ping-Tool with additional Mac-Address information and DNS-Resolv-Name. Need 'ip neigh' as command
Resolve dependencies, merge and minify CSS and JavaScript files with Juicer - the command line tool for frontend engineers
Simple command line tool that resolves your public IP address and accordingly updates DNS record on one of the currently supported (Linode, DigitalOcean) DNS services.
This Gem format of the stdlib module is intended to make it easier for _module authors_ to resolve dependencies using a Gemfile when running automated testing jobs like Travis or Jenkins. The recommended best practice for installation by end users is to use the `puppet module install` command to install stdlib from the [Puppet Forge](http://forge.puppetlabs.com/puppetlabs/stdlib).
This is intended to be used as a mixin, usualy with some kind of library that parses optional command line arguments. The feature here is that the options may contain tags ('example_tag:') that are not resolved until they are used. This means that one option may refer to another. An example might be: --stage /tmp/fred --logfile stage:/my.log which would later provide a method 'logfile' that would return '/tmp/fred/my.log'
A library paring TLA+ language. Gem name `tla-parser-s` because did not want to reserve "officical" `tla-parser` name. Sematic routines create a list of files -names (=modules) needed to satisfy set of entry points. Entry points include names passed as parameters to command line tool (`bin/tla-resolver.rb`), or as API paramters to `TlaParserS::Resolver#resolveModulesDo`.
Lightning is a commandline framework that lets users wrap commands with shell functions that are able to refer to any filesystem path by its basename. To achieve this, a group of paths to be translated are defined with shell globs. These shell globs, known as a lightning _bolt_, are then applied to commands to produce functions. In addition to translating basenames to full paths, lightning _functions_ can autocomplete these basenames, resolve conflicts if they have the same name, leave any non-basename arguments untouched, and autocomplete directories above and below a basename. To make bolts shareable between users and functions easier to create, lightning has _generators_. A _generator_ generates filesystem-specific globs for a bolt. Lightning comes with some default generators. Users can make their own generators with generator plugins placed under ~/.lightning/generators/.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
No description provided.
No description provided.
No description provided.
No description provided.