Node version checker
A version checker for react-native expo applications
A version checker for react-native applications
Version checker for expo applications
A system version checker in Node.js
A version checker for react-native expo applications
Version checker working with GitHub releases.
Determine if your addon is being used by a minimum version of Ember CLI.
The common API used by all version-checker modules.
A version checker for react-native applications
Data version checker function compatible with @reactioncommerce/migrator
Data version checker function compatible with @bugslifesolutions/migrator
Node version checker cli
CLI version of version-checker
JS support version checker
Dead simple in browser Ember / Ember Data version checker. Works with Ember Addons.
`app-version-checker` is a library for checking whether a mobile app is up-to-date or not. It currently supports iOS and Android platforms.
A system version checker in Node.js
A react native module to find the app version on play store and ios app store
A system version checker in Node.js
arXiv paper version checker plugin for dependabit — tracks academic preprint revisions as dependency sources.
Version checker
Runs typescript type checker and linter on separate process.
Version checker for PlexAddons - integrates with addons.plexdev.xyz API
A clean, easy to use version checker built to help you track problems with your dependencies
Checks releases and versions of programs through RSS or Atom feed and tells you.
Rust core KYA (Know Your Agent) validator with Python bindings, TEE support, and blockchain integration
A tool to check for newer versions of Rust crates on crates.io and interactively update them.
Version checker to integrate with your gem
Write a longer description or delete this line.
A gem-style version checker
Gem vulnerability and version checker
jslintrb is a packaged version of Douglas Crockford's JSLint JavaScript code checker. jslintrb uses SpiderMonkey via the Johnson Ruby gem to interpret the JSLint javascript.
Ruby interpreter and version checker.
Hashcash version 1 algorithm generator and checker
This tool is just a simple checker to see if newer versions of Carthage dependencies use keywords that relate to security
Offer end-users a configurable /check route to check their browsers compatibility with your Rails application, with the ability to enable/disable standard checker modules or even add their own module logic in Javascript. Standard checkers are: browser name/version, cookies, asset loading and Pusher connectivity.
A Ruby toolkit for working with BIMI — discovering records, fetching and validating SVG Tiny PS logos, and verifying VMC and CMC certificate chains. This is an early preview release; the public API will grow with subsequent versions. Run BIMI.check in a terminal to see an animated placeholder for the checker that's coming next.
== PintosCheck -- Auto Pintos Checker to Save the Day == == Functionalities == The functionality of this simple script is to download pintos homework assignments from the mail inbox and then run through all the desired tests and finally generate reports in plain text or html formats, all automatically. == Requirements For Running PintosCheck == Since all the scripts are written in ruby, PintosCheck require ruby installed on the system. I use ruby 1.8.7 for development, but ruby 1.9.* versions are expected to function as well. However, ruby 1.8.6 and lower versions are not supported. For information of downloading and installing ruby, see http://www.ruby-lang.org/en/downloads/. In addition to ruby itself, RubyGems 1.3.* is also required because it hosts the installation source for this project and almost all other ruby projects as well. To download or update RubyGems, please go to http://gemcutter.org/pages/download for more information. == Installation == Once you have all the requirements on your system, it's really easy to install PintosCheck. In the UNIX shell or Windows command line environment, type the following command(sudo if needed): gem install pintoscheck --include-dependencies Go grab a cup of coffee, and PintosCheck will automatically download and install itself onto the system. To check the installation, type 'ptschk --version', and if something like 'PintosCheck 0.1.0' pops up then you're green to go! == Finally, how do I check my students' pintos homework? == This project ships with a 'ptschk' command tool. This tool needs a task configuration file to actually do everything. The configuration file is in YAML format, which is basically a recursive key-value pair representation. If you're using PintosCheck for the first time, there's a very nice command line option to generate the skeleton for you. Just run 'ptschk init my_first_task.config' and a file named 'my_first_task.config' will be generated for you. Inside this file there is a set of the minimal options for the task to run properly, and you just have to fill in what you need. After you set up your configuration file, run 'ptschk run my_first_task.config' and the tasks will kick off immediately, and after a while the report will be generated. A detailed configuration options for advanced task setup will be available in production release of this project.
# mdtoc - Markdown Table of Contents Read Markdown files and output a table of contents. ## Installation Requirements: * [Ruby](https://www.ruby-lang.org/en/) (see [.ruby-version](./.ruby-version)) ```bash gem install mdtoc ``` ## Usage ```bash mdtoc --help Usage: mdtoc [options] files or directories... -h, --help Show this message -o, --output PATH Update a table of contents in the file at PATH -a, --[no-]append Append to the --output file if a <!-- mdtoc --> tag isn't found -c, --[no-]create Create the --output file if it does not exist ``` 1. Add a `<!-- mdtoc -->` tag to a Markdown file. ```bash echo '<!-- mdtoc -->' >> README.md ``` 2. Run `mdtoc` and specify input files or directories (eg. the "test/samples" directory) and an output file (eg. "README.md"). ```bash mdtoc -aco README.md test/samples ``` ## Example Rakefile Create a `Rakefile` with the contents below, then run [`rake`](https://github.com/ruby/rake) to: * `git pull` * `git add` any `*.md` files * Run `mdtoc` to update the generated table of contents in the ./README.md file * Git commit and push any changes ```ruby task default: %w[mdtoc] desc 'Update Markdown table of contents and push changes to the git repository' task :mdtoc do command = <<~CMD set -e if [ -n "$(git diff --name-only --diff-filter=U)" ]; then echo 'Error: conflicts exist' >&2 exit 1 fi mdtoc --append --create --output README.md docs/ git add *.md **/*.md git commit -qm 'Update TOC' || true git pull git push CMD sh command, verbose: false do |ok, status| unless ok fail "Failed with status: #{status.exitstatus}" end end end ``` See [andornaut/til](https://github.com/andornaut/til/blob/master/Rakefile) for an example. ## Development ### Setup Requirements: * [Bundler](https://bundler.io/) * [chruby](https://github.com/postmodern/chruby) (recommended) ```bash # Setup development environment bin/setup ``` ### Tasks ```bash # List rake tasks rake -T rake build # Build gem into the pkg directory rake default # Run the build, rubocop, sorbet and test tasks rake install # Build and install gem into system gems rake rubocop # Run RuboCop rake sorbet # Run the Sorbet type checker rake test # Run tests # Run mdtoc with test inputs ruby -Ilib bin/mdtoc test/samples # Run mdtoc with test inputs, and write to a newly created output file f=$(mktemp) && ruby -Ilib bin/mdtoc -aco ${f} test/samples ; cat ${f} ``` ### Publishing 1. Bump version in `lib/mdtoc/version.rb` 2. Run `bundle install` to update `Gemfile.lock` 3. Commit the changes 4. Run `rake release` to publish the gem to RubyGems, create the git tag, and push
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.