Optional dependencies are not for running tests #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Makes sense to me. |
benjamn
added a commit
that referenced
this pull request
Oct 31, 2013
Optional dependencies are not for running tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed, optionalDependencies is for when the installation of a dependency may fail on certain operating systems or in certain network conditions, and the module is capable of working around this. e.g. when you have a native C++ version of something, but also a JavaScript fallback to use in development.
Optional dependencies still get installed by anyone depending on your module even though they are not needed.
devDependencieson the other hand, are only installed by people trying to run you tests (e.g. travis-ci)