deps
Here are 50 public repositories matching this topic...
Some of the integration tests evaluate that certain words are present in the stdout output, which can break or change with updates to the logging verbosity. The following tests specifically do this:
integration/update/empty-deps
integration/u
-
Updated
May 31, 2019 - Clojure
-
Updated
Jan 30, 2019 - Go
-
Updated
Dec 13, 2020 - Shell
-
Updated
Mar 9, 2020 - JavaScript
-
Updated
Nov 9, 2020 - Lua
Right now, when we want to add a common directory to ignore, we need to go to each integration and add an item. Adding support for some common global ignores would be really useful. Some common directories to ignore are often:
vendor/
test/
testdata/
hack/
-
Updated
Feb 3, 2015 - JavaScript
-
Updated
Dec 11, 2020 - TypeScript
-
Updated
Aug 25, 2018 - JavaScript
-
Updated
Jun 1, 2020 - JavaScript
-
Updated
May 26, 2020 - PHP
-
Updated
Nov 2, 2020 - PHP
Improve this page
Add a description, image, and links to the deps topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the deps topic, visit your repo's landing page and select "manage topics."
Optional dependencies should not be treated as a "dependency" kind, of which there are only three -- regular, build, and dev. "Optional deps" should instead be handled as a boolean flag, which is what
cargodoes. A dependency can be both a build dependency and optional simultaneously, but currently cargo-deps will erase one of these.Optional dependencies can be displayed with a dashed line.