Update zone.js to version 0.6.14 🚀 #351
Reference in New Issue
Block a user
Delete Branch "greenkeeper-zone.js-0.6.14"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello lovely humans,
zone.js just published its new version 0.6.14.
This version 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 zone.js.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 26 commits .
76acf6echore(release): version bump and dist for 0.6.143a054befeat(jasmine): patch jasmine to understand zones.6ef7451chore: clean up imports4942b4afeat(trackingZone): Keep track of tasks to see outstanding tasks.1883589chore(release): version bump and dist for 0.6.135f519defeat(jasmine): Switch jasmine patch to use microtask and preserve zone.fd1dfccfix(fakeAsync): throw error on rejected promisees.0621014feat(zone): Add Zone.getZone api2d02e39feat(ProxySpec): create a ProxySpec which can proxy to other ZoneSpecs.dafad98fix(promise): allow Promise subclassing6df5f93fix: throw if trying to load zone more then once.7b9a00cchore: correct typod43b4b8fix(build): fix broken master due to setTimeout not returning a number on nodedbcfb32Pass actual error to failCallback (#383)80ae6a8feat: return timeout Id in ZoneTask.toString (fixes #341)There are 26 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgradePull request closed