Suppress dependency deprecation warnings #108
Merged
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
These are annoying and there's little that users can do about it. Most of these come from e.g. transitive Jest dependencies, and Jest has open issues tracking the migration to supported dependencies.
🦋 Changeset is good to goLatest commit: 9e7359a We got this. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
etaoins
approved these changes
Jun 24, 2020
| const str = Buffer.from(chunk).toString(); | ||
|
|
||
| // Filter out annoying deprecation warnings that users can do little about | ||
| if (!str.startsWith('warning skuba >')) { |
There was a problem hiding this comment.
When I read the PR description I was excited to figure out which Yarn argument did this.
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.
These are annoying and there's little that users can do about it. Most of these come from e.g. transitive Jest dependencies, and Jest has open issues tracking the migration to supported dependencies.