summaryrefslogtreecommitdiff
path: root/deps/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/are-we-there-yet/CHANGES.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/are-we-there-yet/CHANGES.md')
-rw-r--r--deps/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/are-we-there-yet/CHANGES.md19
1 files changed, 0 insertions, 19 deletions
diff --git a/deps/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/are-we-there-yet/CHANGES.md b/deps/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/are-we-there-yet/CHANGES.md
deleted file mode 100644
index e990b86ddf..0000000000
--- a/deps/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/are-we-there-yet/CHANGES.md
+++ /dev/null
@@ -1,19 +0,0 @@
-Hi, figured we could actually use a changelog now:
-
-## 1.1.1 2016-01-29
-
-* Fix a typo in stream completion tracker
-
-## 1.1.0 2016-01-29
-
-* Rewrote completion percent computation to be low impact– no more walking a
- tree of completion groups every time we need this info. Previously, with
- medium sized tree of completion groups, even a relatively modest number of
- calls to the top level `completed()` method would result in absurd numbers
- of calls overall as it walked down the tree. We now, instead, keep track as
- we bubble up changes, so the computation is limited to when data changes and
- to the depth of that one branch, instead of _every_ node. (Plus, we were already
- incurring _this_ cost, since we already bubbled out changes.)
-* Moved different tracker types out to their own files.
-* Made tests test for TOO MANY events too.
-* Standarized the source code formatting