Get the first path that exists on disk of multiple paths
Get the first fulfilled promise that satisfies the provided testing function
locate-path callback ver.
[](https://www.npmjs.com/package/@aws-sdk/util-locate-window) [](https://www.npmjs.com/packag
Find apps installed on your system. This util will help to find executables of a known app like Chrome, Firefox,... on Windows, Linux, and macOS out of the box.
Get the line and column number of a specific character in a string
Get the first path that exists on disk of multiple paths
Locate a program or locally installed node module's executable
Get the first path that exists on disk of multiple paths
Get the first path that exists on disk of multiple paths
No description provided.
Unzip cross-platform streaming API
Locates JAVA_HOME on any platform, and can differentiate between different versions.
The `ao` Scheduler Utils provides an abstraction for retrieving the location of an `ao` Process' Scheduler, and checking whether a wallet is a valid `ao` Scheduler
TypeScript definitions for locate-chrome
No description provided.
Facilities to manage artifacts and their dependencies in your Node.js applications. The module exposes TypeScript/JavaScript APIs and decorators to register artifacts, declare dependencies, and resolve artifacts by keys. It also serves as an IoC container
Find Google Chrome on your system
Locating midway application locations
Provides a fallback for non-existing directories so that the HTML 5 history API can be used.
text ===========
Finds the common standard cache directory
Hundreds of open source icon sets in IconifyJSON format
A developer-friendly secrets detection tool for CI and pre-commit hooks based on Yelp's detect-secrets
Devel::Which provides an effective definition finder, for example, Fixnum#nonzero? is defined at Numeric and Fixnum.which_method("nonzero?") returns Numeric.
Locates a program file in the user's path. The which method takes a list of command names and searches the path for each executable file that would be run had these commands actually been invoked.
Parses RSpec error output to provide a summary showing what errors were encountered, the number of occurrences per error, and file path and line number locations
This Asciidoctor extension exposes a variable `indir`, which holds the path to the directory where the current asciidoc file is located. The value of this variable changes to always reflect the location of the current, included subdocument. (Note, this is in contrast to the `docfile` variable, which remains the same throughout an entire document).
A ruby gem adaptation of the shotgun screenshot tool for linux. Creates a .pam screenshots at a given path and returns the location.
Adds the bower directory to the sprockets path so that you can require bower components. Relies on the .bowerrc on the root of the project to locate the right directory.
This Asciidoctor extension exposes a variable `indir`, which holds the path to the directory where the current asciidoc file is located. The value of this variable changes to always reflect the location of the current, included subdocument. (Note, this is in contrast to the `docfile` variable, which remains the same throughout an entire document).
Fork of bundled mkmf.rb, should work as drop in replacement. Modifications: * GDB and XCode path compatibility: relative path specified by mkmf (../../../../ext/<target>/...) confuses source-to-debug correspondence. The downside to this is that mkmfmf specifies absolute paths, which means that the project will have to be recompiled for debugging from an alternate location. This can be disabled by adding a use_relative_paths block. * CURRENTLY NOT WORKING: Sub-directory support for source code: all .c, .m, .cc, .cxx., .cpp files and if the filesystem is case sensitive, all .C files are automatically included, and any directories with .h files are added to INCFLAGS. * Automatically uses CC from ENV if set
This gem has been built to ease usage of multiple versions of command line tools like Ruby, Python, Vagrant, etc. It is not installer, it's a tool to switch between already installed versions of a software. By using a configuration file and some conventions, the tool will be able to locate your program and switch between multiple version of it be tweaking your environment variables, usually simply the PATH one.
Clean interface to discover configuration file locations forAI coding assistants (Claude Code, OpenCode, Codex). Shows global and project config paths, handles environment variable overrides, and determines which config is effective based on precedence rules.
Chef-Berksfile-Env ================== A Chef plugin which allows you to lock down your Chef Environment's cookbook versions with a Berksfile. This is effectively the same as doing `berks apply ...` but via `knife environment from file ...`. View the [Change Log](https://github.com/bbaugher/chef-berksfile-env/blob/master/CHANGELOG.md) to see what has changed. Installation ------------ /opt/chef/embedded/bin/gem install chef-berksfile-env Usage ----- In your chef repo create a Berksfile next to your Chef environment file like this, chef-repo/environments/[ENV_NAME]/Berksfile This is the default location that will used by the plugin. We have to put the Berksfile in its own directory since [multiple Berksfiles can't exist in the same directory](https://github.com/berkshelf/berkshelf/issues/1247). The berksfile should include any cookbooks that your nodes or roles explicitly mention for that environment, source "https://supermarket.getchef.com" cookbook "java" cookbook "yum", "~> 2.0" ... Next we need to generate our Berksfile's lock file, berks install Your environment file must by in `.rb` format and look like this, require 'chef-berksfile-env' # The name must be defined first so we can use it to find the Berksfile name "my_env" # Load Berksfile locked dependencies as my environment's cookbook version contraints load_berksfile ... Now our environment will use the locked versions of the cookbooks and transitive dependencies generated by our Berksfile. Upgrading to the latest dependecies is now as simple as, berks install Our Berksfile also provides an easy way to ensure all the cookbooks and their versions that our environment requires are uploaded to our chef-server, berks upload How the Plugin Finds the Berksfile ---------------------------------- If you are curious how the plugin knows to find the Berksfile in `chef-repo/environments/[ENV]/Berksfile`, you want to put your Berksfile somewhere else or you have run into this error `Expected Berksfile at [/path/../Berksfile] but does not exist`, this section will explain how this works and ways to tweak the path or fix your error. `load_berksfile` has an optional argument which represents the path to your Berksfile. This path can be pseduo relative (explained in a moment) or absolute. By default the value is `environments/[ENV_NAME]/Berksfile`. By pseduo relative I mean that its a relative path but the plugin will check to see if the directory we are executing from partially matches our relative path. So if we are running knife from `/home/chef-repo/environments` and our relative path is `chef-repo/environments/dev/Berksfile` the plugin will see that the relative path is partially included in our execution directory and will attempt to merge the two to come up with `/home/chef-repo/environments/dev/Berksfile`. If we can't make any match at all we attempt to guess the path by just joining the relative path with our execution directory. So why do we do this? Well the only way to use this plugin is if your environment is in Ruby format. Chef's `knife from file ...` uses Ruby's `instance_eval` in order to do this. This means the code on Chef's end effectively looks like this, env.instance_eval(IO.read(env_ruby_file)) which means that any context about the location of the environment file is lost. So we have no great way to discern the location of our environment Ruby file, so instead we guess.
magicprotorb lets you `require "magicprotorb/foo/bar_pb"` and have foo/bar.proto compiled to descriptors and registered at require time. The dotted require path mirrors the canonical proto path 1:1, so the require name, the file location, and the descriptor name can never drift apart. A small Rust extension (built on the pure-Rust protox compiler) turns .proto text into a FileDescriptorSet, which is then registered through the stock protobuf DescriptorPool — making the resulting message classes indistinguishable from generated ones.
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.