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.
This patch updates all outdated development dependencies, but does
not upgrade the two outdated production dependencies.
breaking change that is difficult to address (see Remove shrinkwrap, lock swagger, and major update to WS #47 for details).
that includes breaking changes. See
http://bluebirdjs.com/docs/new-in-bluebird-3.html for details.
These are workable changes for node-ari-client, but we expose
bluebird Promises on our public API, so updating this would require
a major version bump.
For changes in the development dependencies, see the following
changelog entries:
No details regarding the major version bump of hock could be found,
but it had a substantial change to its public api. Namely, it does not
handle any of the actual http server stuff for you anymore. Changes
are included in this PR to adapt the tests to this new api.
There are still some npm install warnings even after updating these
dependencies:
The fix for this is already in the jshint master branch, but no
npm version has been cut for it yet. For additional details, see
Update minimatch version jshint/jshint#2952
wrench being completely deprecated in favor of another library,
and the marked package not being meant to be installed as a dep.
Upon investigation, it seems that the jsdoc package has actually
been abandoned, so we need to start thinking about migrating away
from it. Ticket replace jsdoc with a non-abandoned project #55 has been opened to investigate this.
installed as a dep. This isn't really worth looking into, as we
are gradually moving away from grunt anyway.