test-all-versions - Run your test suite against all published versions of a dependency

  •        3

Run your test suite against all published versions of a given dependency.If tav is run without specifying a module, it will instead look for a .tav.yml file in cwd and expect that to contain all its configuration. This is similar to how Travis CI works with .travis.yml.

https://github.com/watson/test-all-versions#readme

Dependencies:

after-all-results : ^2.0.0
ansi-diff-stream : ^1.2.0
cli-spinners : ^1.1.0
fresh-require : ^1.0.3
is-ci : ^1.0.10
js-yaml : ^3.7.0
log-symbols : ^2.1.0
minimist : ^1.2.0
npm-package-versions : ^1.0.1
once : ^1.4.0
resolve : ^1.2.0
semver : ^5.1.0
spawn-npm-install : ^1.2.0

Tags
Implementation
License
Platform

   




Related Projects

meteor-autoform - AutoForm is a Meteor package that adds UI components and helpers to easily create basic forms with automatic insert and update events, and automatic reactive validation

  •    Javascript

AutoForm is a Meteor package that adds UI components and helpers to easily create basic forms with automatic insert and update events, and automatic reactive validation. Versions 6+ of this package require that you separately install the simpl-schema NPM package. Prior versions require and automatically install the simple-schema Meteor package. You can optionally use it with the collection2 package, which you have to add to your app yourself. AutoForm 6.0 is now available and requires switching your app to using the SimpleSchema package from NPM. Be sure to check out the change log for full details. Note that if you use add-on packages that haven't been updated yet, you will not yet be able to update to version 6.

npm-check-updates - Find newer versions of package dependencies than what your package

  •    Javascript

npm-check-updates upgrades your package.json dependencies to the latest versions, ignoring specified versions. npm-check-updates maintains your existing semantic versioning policies, i.e., it will upgrade your "express": "^4.0.0" dependency to "express": "^5.0.0".

Glide - Package Management for Golang

  •    Go

Are you used to tools such as Cargo, npm, Composer, Nuget, Pip, Maven, Bundler, or other modern package managers? If so, Glide is the comparable Go tool. Manage your vendor and vendored packages with ease. Glide is a tool for managing the vendor directory within a Go package. This feature, first introduced in Go 1.5, allows each package to have a vendor directory containing dependent packages for the project. These vendor packages can be installed by a tool (e.g. glide), similar to go get or they can be vendored and distributed with the package.

Julia.jl - Curated decibans of Julia language.

  •    Julia

Julia.jl aggregates and curates decibans of knowledge resources for programming in Julia, an all-purpose programming language that addresses the needs of high-performance numerical analysis and computational science. For Base packages, check if the package you seek is listed in the built-in package manager on github, or check METADATA for registered Julia packages, then use the built-in package manager to install it after checking the requirements for respective versions. Pkg3.jl is an alpha next-generation package manager for Julia that creates a Manifest.toml file that records the exact versions of each dependency and their transitive dependencies.

spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers

  •    Python

Spack is a multi-platform package manager that builds and installs multiple versions and configurations of software. It works on Linux, macOS, and many supercomputers. Spack is non-destructive: installing a new version of a package does not break existing installations, so many configurations of the same package can coexist. Spack offers a simple "spec" syntax that allows users to specify versions and configuration options. Package files are written in pure Python, and specs allow package authors to write a single script for many different builds of the same package. With Spack, you can build your software all the ways you want to.


kicad-ESP8266 - Schematic symbols and PCB footprints for ESP8266 modules

  •    OpenSCAD

This project has both schematic symbols, footprints, and 3d models for ESP8266 based modules. It is a work-in-progress. Additions and corrections are welcome. Enter a pull request or file an issue on GitHub. ESP-01 - Note that there are two versions of this module available on open market. The schematic symbol is for the v090 version which is probably the same as the v080. There is an older version that does not include any GPIO signals. The footprint is the same for all of the ESP-01 modules.

XposedTools - These tools can be used to compile and package the Xposed framework.

  •    Perl

These tools can be used to compile and package the Xposed framework. They are especially useful when it comes to releasing files for various platforms and Android versions. Note that Xposed by itself is quite complicated and not suitable for beginners. You'll need a certain level of experience with C++ and general software development in order to build and modify Xposed by yourself. Xposed is open-source and contributions are very welcome. The files in this repository hopefully make it easier to compile custom versions for testing and improvements. However, please be careful when you publish your own versions. Make clear that it's an unofficial version to avoid confusion, and also remember to give proper attribution. Your version probably still includes 99% or more of the original source code that has been written since 2012, so it wouldn't be fair to make it sound like you did all the work. Also, if you made some fixes or improvements, it's in everyone's interest that you create a pull request and contribute them back to the original project.

luarocks - LuaRocks is the package manager for the Lua programming language.

  •    Lua

A package manager for Lua modules. It allows you to install Lua modules as self-contained packages called rocks, which also contain version dependency information. This information can be used both during installation, so that when one rock is requested all rocks it depends on are installed as well, and also optionally at run time, so that when a module is required, the correct version is loaded. LuaRocks supports both local and remote repositories, and multiple local rocks trees. You can download and install LuaRocks on Unix and Windows.

nodenv - Manage multiple NodeJS versions.

  •    Shell

Use nodenv to pick a Node version for your application and guarantee that your development environment matches production. Put nodenv to work with npm for painless Node upgrades and bulletproof deployments. Powerful in development. Specify your app's Node version once, in a single file. Keep all your teammates on the same page. No headaches running apps on different versions of Node. Just Works™ from the command line. Override the Node version anytime: just set an environment variable.

updtr - Update outdated npm modules with zero pain™

  •    Javascript

Based on npm outdated, updtr installs the latest version and runs npm test for each dependency. In case the test succeeds, updtr saves the new version number to your package.json. Otherwise, updtr rolls back the conflicting update. Additionally, it will use yarn instead of npm when a yarn.lock file is present in your project.

rez - An integrated package configuration, build and deployment system for software

  •    Python

Rez is a cross-platform package manager with a difference. Using Rez you can create standalone environments configured for a given set of packages. However, unlike many other package managers, packages are not installed into these standalone environments. Instead, all package versions are installed into a central repository, and standalone environments reference these existing packages. This means that configured environments are lightweight, and very fast to create, often taking just a few seconds to configure despite containing hundreds of packages. See the wiki for full documentation.

lts - Enforces Long Term Supported versions of Symfony components

  •    

Using symfony/symfony makes Composer install all Symfony Components, all in the same version. But when using the standalone packages, Composer might install dependencies in a different major version (symfony/http-kernel v3.4 is compatible with symfony/event-dispatcher v4.0 for instance). This is fine if you don't want to stick to Symfony LTS versions and if your code does not use these transitive dependencies.

rollup-starter-project - Sample project for packages built using rollup.

  •    Javascript

This package shows how to get started with rollup (and babel) for writing npm packages using ES6 modules. Writing npm packages with a jsnext:main allows users of your package to choose whether they use it using the traditional require function understood by node.js, or using the import statement added in ES6 which can result in smaller bundles through live-code inclusion static analysis.You can simply use this project as inspiration for how to configure your own, or clone it and edit the metadata files when starting your own project (i.e. README.md, package.json, and LICENSE).

goop - A simple dependency manager for Go (golang), inspired by Bundler.

  •    Go

A dependency manager for Go (golang), inspired by Bundler. It is different from other dependency managers in that it does not force you to mess with your GOPATH. Run goop install. This will install packages inside a subdirectory called .vendor and create Goopfile.lock, recording exact versions used for each package and its dependencies. Subsequent goop install runs will ignore Goopfile and install the versions specified in Goopfile.lock. You should check this file in to your source version control. It's a good idea to add .vendor to your version control system's ignore settings (e.g. .gitignore).

puppet-sandbox - A Vagrant-based Puppet development environment for creating new modules

  •    Puppet

Puppet Sandbox is a multi-VM Vagrant-based Puppet development environment used for creating and testing new modules outside of your production environment. It is prefered over the upstream Learning Puppet VM as it gives you more flexibility and allows you to use your own local editing environment and tools. These VMs can be used in conjunction to segregate and test your modules based on node roles, Puppet environments, etc. You can even test modules on different Linux distributions or release versions to better match your production infrastructure.

micropython-lib - Core Python libraries ported to MicroPython

  •    Python

Note that the main target of micropython-lib is a "Unix" port of the aforementioned fork of MicroPython. Actual system requirements vary per module. Majority of modules are compatible with the upstream MicroPython, though some may require additional functionality/optimizations present in the "advanced" fork. Modules not related to I/O may also work without problems on bare-metal ports, not just on "Unix" port (e.g. pyboard). micropython-lib packages are published on PyPI (Python Package Index), the standard Python community package repository: https://pypi.org/ . On PyPI, you can search for MicroPython related packages and read additional package information. By convention, all micropython-lib package names are prefixed with "micropython-" (the reverse is not true - some package starting with "micropython-" aren't part of micropython-lib and were released by 3rd parties).

node-gyp - Node.js native addon build tool

  •    Python

node-gyp is a cross-platform command-line tool written in Node.js for compiling native addon modules for Node.js. It bundles the gyp project used by the Chromium team and takes away the pain of dealing with the various differences in build platforms. It is the replacement to the node-waf program which is removed for node v0.8. If you have a native addon for node that still has a wscript file, then you should definitely add a binding.gyp file to support the latest versions of node.Multiple target versions of node are supported (i.e. 0.8, ..., 4, 5, 6, etc.), regardless of what version of node is actually installed on your system (node-gyp downloads the necessary development files or headers for the target version).

next-update - Tests if module's dependencies can be updated to latest version

  •    Javascript

Note I no longer maintain Node 0.12/4 compatibility. Please switch to Node 6. Both package.json file and node_modules folder are left unchanged, and now you know that you can safely upgrade both libraries to later versions.

istanbul - Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests

  •    Javascript

Deprecation Notice: this version of istanbul is deprecated, we will not be landing pull requests or releasing new versions. But don't worry, the Istanbul 2.0 API is now available and is being actively developed in the new istanbuljs organization. The best way to see it in action is to run node unit tests. Say you have a test script test.js that runs all tests for your node project without coverage.

pacote - programmatic npm package and metadata downloader

  •    Javascript

pacote is a Node.js library for downloading npm-compatible packages. It supports all package specifier syntax that npm install and its ilk support. It transparently caches anything needed to reduce excess operations, using cacache. The pacote team enthusiastically welcomes contributions and project participation! There's a bunch of things you can do if you want to contribute! The Contributor Guide has all the information you need for everything from reporting bugs to contributing entire new features. Please don't hesitate to jump in if you'd like to, or even ask us questions if something isn't clear.