Remove deprecation warning during npm install
#195
Closed
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
I realize this shouldn't be strictly necessary, because the loose semver range should pick up this version bump automatically. However, this commit pins the coffee-script dep at 1.12.6 to make sure (especially with some of the NPM 5 edge case issues folks have been experiencing as of late). It also locks to an exact dependency, for the same reasons as laid out here in this PR to the main `grunt` package: gruntjs/grunt#1556 (comment)
|
updated to 2 in #196 |
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.
I realize this shouldn't be strictly necessary, because the loose semver range should pick up this version bump automatically. However, this commit pins the coffee-script dep at 1.12.6 to make sure (especially with some of the NPM 5 edge case issues folks have been experiencing as of late). It also locks to an exact dependency, for the same reasons as laid out here in this PR to the main
gruntpackage: gruntjs/grunt#1556 (comment)