diff options
| author | nanalelfe <nargiza.nosirova@mail.utoronto.ca> | 2016-07-28 02:20:52 +0000 |
|---|---|---|
| committer | nanalelfe <nargiza.nosirova@mail.utoronto.ca> | 2016-07-28 02:20:52 +0000 |
| commit | 4cff38c8f7b65dab1fd72ea835ea7288327d1056 (patch) | |
| tree | ac93acd69e77eef1e352af953d56238d70ea9c5d /node_modules/es6-promise/CHANGELOG.md | |
| parent | e11dd98c9a55cd1742d221e3b1ea90d31e240fa8 (diff) | |
Fixed admin bug
Diffstat (limited to 'node_modules/es6-promise/CHANGELOG.md')
| -rw-r--r-- | node_modules/es6-promise/CHANGELOG.md | 29 |
1 files changed, 0 insertions, 29 deletions
diff --git a/node_modules/es6-promise/CHANGELOG.md b/node_modules/es6-promise/CHANGELOG.md deleted file mode 100644 index fbe4053..0000000 --- a/node_modules/es6-promise/CHANGELOG.md +++ /dev/null @@ -1,29 +0,0 @@ -# Master - -# 3.0.2 - -* correctly bump both bower and package.json versions - -# 3.0.1 - -* no longer include dist/test in npm releases - -# 3.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 described at https://github.com/cujojs/when/issues/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); - -# 2.0.0 - -* re-sync with RSVP. Many large performance improvements and bugfixes. - -# 1.0.0 - -* first subset of RSVP |
