Update dependency es6-promise to v4
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| es6-promise | ^2.0.1 -> ^4.0.0 |
Release Notes
stefanpenner/es6-promise (es6-promise)
v4.2.8
v4.2.7
v4.2.6
v4.2.5
- remove old try/catch performance hacks, modern runtimes do not require these tricks
v4.2.4
- [Fixes #305] Confuse webpack
v4.2.3
- Cleanup testem related build configuration
- Use
prepublishOnlyinstead ofprepublish(thanks @rhysd) - Add Node.js 9, 8 to testing matrix
- drop now unused s3 deployment files
- internal cleanup (thanks to @bekzod, @mariusschulz)
- Fixup Changelog
v4.2.2
- Ensure PROMISE_ID works correctly
- internal cleanup (thanks yo @mariusschulz)
v4.2.1
- drop bower support
v4.2.0
- drop
distfrom git repo - add
Promise.prototype.finally - update various build related dependencies
- add CDN links
v4.1.1
v4.1.0
v4.0.5
- fix require('es6-promise/auto') for Node < 4
v4.0.4
- fix asap when using https://github.com/Kinvey/titanium-sdk
v4.0.3
- fix Readme links
v4.0.2
- fix require('es6-promise/auto');
v4.0.1
v4.0.0
- no longer polyfill automatically, if needed one can still invoke
require('es6-promise/auto')directly.
v3.3.1
- fix links in readme
v3.3.0
- support polyfil on WebMAF (playstation env)
- fix tampering related bug global
constructorwas referenced by mistake. - provide TS Typings
- increase compatibliity with sinon.useFakeTimers();
- update build tools (use rollup)
- directly export promise;
v3.2.1
- fix race tampering issue
- use eslint
- fix Promise.all tampering
- remove unused code
- fix issues with NWJS/electron
v3.1.2
- fix node detection issues with NWJS/electron
v3.0.2
- correctly bump both bower and package.json versions
v3.0.1
- no longer include dist/test in npm releases
v3.0.0
-
use nextTick() instead of setImmediate() to schedule microtasks with node 0.10. Later versions of nodes are not affected as they were already using nextTick(). Note that using nextTick() might trigger a depreciation warning on 0.10 as descrhttps://github.com/cujojs/when/issues/410sues/410. The reason why nextTick() is preferred is that is setImmediate() would schedule a macrotask instead of a microtask and might result in a different scheduling. If needed you can revert to the former behavior as follow:
var Promise = require('es6-promise').Promise; Promise._setScheduler(setImmediate);
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.