Check if a path exists
Check if a path exists
Test whether a path exists on the filesystem.
Synchronously check if a path exists and returns its stats object if it does
Ensures that the file path exists.
check if a path exists, supports arrays
Check if a certain path exists and is a file (i.e. not a folder)
A lightweight fork of [eslint-plugin-require-path-exists](https://github.com/BohdanTkachenko/eslint-plugin-require-path-exists) that only checks CSS files.
Check if a path exists
Tests whether a path exists on the filesystem.
Plugin check-path-exists for bundler Vite
Test whether a path exists on the filesystem.
Checks all require path's to exist as files
Check if a path exists
Check if a path exists.
Utility function to ensure a directory path exists and return a Promise
Ensure path exists
Type definitions for path-exists 1.0.0 from https://www.github.com/DefinitelyTyped/DefinitelyTyped
> Check if a path exists
path-exists — a lightweight utility by @akashadubey
Emits an error if output.path or custom path exists (or not exists)
[DepUp] Check if a path exists
moocba-cli path-exists
基于fs-extra, path-exists集成的路径判断工具
CLI crate for nils-agent-docs in the nils-cli workspace.
Interactive CLI input tool with real-time validation and choice menus
Core domain logic for eden-skills: config, plan, lock, reactor, adapter, registry, and safety
Capistrano plugin that ensures the `deploy_to` deployment path exists and has the right permissions.
An RSpec matcher that checks if a given path exists.
Identify the used framework of a given project.
It should extract and test file paths from a variety of documents, but this is a "quick-and-dirty" solution intended only to cover common use cases.
Findex indexes files in a path recursively, updates existing ones and deletes removed files from the index
Utility for defining a path that, if the file exists, is deleted at the end of the block.
Jekyll plugin to generate src attribute for an img tag with the given image, and also the srcset with an appropriate @2x path for the image if one exists on the filesystem.
RAliasFile is a C extension to Ruby aimed to resolve alias file on Mac OS X 10.+. It also provides means to check if the alias file is broken, it's target is a folder or file, the given path does exists.
namespace_editor replaces existing namespaces with a new namespace in each source file found at the given source path whose extension is one of those in the given list of extensions. Useful for Android white label apps
Rumodule is used to manage shell environment variables by adding/removing modules. By adding a module using Rumodule, for example the PATH environment variable can be setup so that the executable is found. Modules exist per tool or per tool version. Rumodule makes it easy to maintain and provide tool setups between multiple users.
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.
SimpleFileCache writes a ruby object to a binary file so that it can be retrieved later from the disk rather than recomputed from scratch. It defines a single method #load_or_recompute that receives a file path and a block. If the file exists and is recent (last changed today), it returns the file contents read with Marshal#load. Otherwise, it executesthe block, saves its return value with Marshal#dump and returns the new data.
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.
No description provided.
No description provided.