Upgrade karma-chrome-launcher to version 3.0.0 #277
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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Pull Request Test Coverage Report for Build 1181
💛 - Coveralls |
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ karma-chrome-launcher (^2.2.0 → ^3.0.0) · Repo · Changelog
Release Notes
3.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 33 commits:
chore: release v3.0.0chore: update contributorsMerge pull request #202 from johnjbarton/depschore: update npm audit fix --forceMerge pull request #197 from rgant/enable-automationEnable Automation for default Chrome BrowserMerge pull request #193 from karma-runner/chore/update-dependencieschore: update karma, grunt and related packageschore: bump standard to latest and fix lintchore: bump mocha, chai and sinon to latestrefactor: swap out fs-access for core fsfeat: allow overriding of the default debug portMerge pull request #192 from karma-runner/chore/update-supported-node-versionschore: remove node 4 from travisMerge pull request #168 from abbotto/patch-1Update README.mdMerge pull request #157 from brutalcrozt/dev-enterMerge pull request #159 from mgol/mailmapchore: add a Git .mailmap with my new nameupdate devDependencies,docs: update headless chrome/puppeteer exampledocs: fix chrome headless code snippetMerge pull request #151 from Fidge123/patch-1Fix typo in READMEMerge pull request #150 from karma-runner/update-travis-to-use-latest-majorschore: update travis to use latest node majorsMerge pull request #149 from frsimond/patch-1Switch from 'Chrome' to 'Chromium'Merge pull request #145 from nimi/puppeteer-docsdocs(README): Fix code example for Puppeteer notesMerge pull request #144 from layershifter/docs/puppeteerdocs(README): add notes about Puppeteerchore(travis): run on working node versionsDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands