Update browserslist to fix out-of-date caniuse-lite messages #20709
Conversation
This file contains hidden or 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
nerrad
added
[Type] Bug
|
Size Change: -6 B (0%) Total Size: 864 kB
ℹ️ View Unchanged
|
draganescu
approved these changes
Mar 8, 2020
Contributor
draganescu
left a comment
draganescu
left a comment
There was a problem hiding this comment.
This fixes Travis failing with
["Browserslist: caniuse-lite is outdated. Please run next command `npm update`"]
jorgefilipecosta
pushed a commit
that referenced
this pull request
Mar 10, 2020
jorgefilipecosta
pushed a commit
that referenced
this pull request
Mar 10, 2020
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.
Description
Running
npm run test-uniton master was returning this error for thepackages/browserslist-config/test/index.test.jstest:In this pull I updated the npm
browserslistpackage which seems to fix the error.How has this been tested?
Unit test execution should result in no errors (I ran locally after the package update and all green for me).