Update web-component-tester to the latest version 🚀 - #12
Open
greenkeeper[bot] wants to merge 1 commit into
Open
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
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.
Version 6.0.0 of web-component-tester just got published.
The version 6.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of web-component-tester.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 119 commits ahead by 119, behind by 2.
a57565a6.0.09de0461Whitespace change.4b36ac8Prepare to release v6.0.0 (#544)afa9812Remove the warning about no local node_modules install of wct. (#500)08a5869Merge pull request #542 from Polymer/polyservefb39d57update wct-local@^2.0.15 (#541)96f7909Fix tsc 2.3.0 warnings. (#543)1aa04b5update polyserver to 0.19.09ade01abump version.2877765Merge pull request #537 from Polymer/wc-ready-checkf533c18remove extra spaces712a66eAvoid relying on filename and instead use an explicit signal:1bbe898Check webcomponents script for "webComponentsReady" flagad599636.0.0-prerelease.9173b290Rungulp buildfromnpm run build; check in new browser.js.mapThere are 119 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴