Added Node.js 7 to package.json. This way yarn will not complain when
Node.js 7 is used. Tests still pass and the code itself also works
on Node.js 7.
Configure Travis CI to run the build on Node.js 7 too, in order to
verify correctness.
Add bind:true option to getCurrentContext
Workaround issue #17 with cujojs/when v3.7.7 due to the fact
that it internally uses a mechanism of user-land queuing for
async-related operations, and possibly issues with similar
packages using queuing (mostly Promise libraries)
* Rework README, add info from docs site (Miroslav Bajtoš)
* Drop continuation-local-storage, use cls-hooked (josieusa)
* Update paid support URL (Siddhi Pai)
* Add app using loopback-context (Amir Jafarian)
* Drop support for Node v0.10 and v0.12 (Siddhi Pai)
* Start the development of the next major version (Siddhi Pai)
* Update deps to loopback 3.0.0 RC (Miroslav Bajtoš)
* make warning less ambigious (Carl Fürstenberg)
Rework the initial section, simplify warnings and installation
instructions.
Update the "Usage" section with content from docs site, as was found in
[Using-current-context.md](http://bit.ly/2hNJSBN).
Rework the module to use the new cls-hooked module (which uses AsyncWrap
available since Node v4.5) instead of old continuation-local-storage
(based on very unreliable async-listener).
Rename "per-request-context" middleware to shorter "per-request".
Introduce "LoopBackContext.perRequest" as a shortcut for way too long
"loopback-context/server/middlewar/per-request"
As soon as CLS module is loaded, the instrumentation/patching of
async-listener is fired. This may cause stack overflows due to promise
instrumentation.
By loading CLS module lazily (only when used for real), we avoid
this kind of problems in applications that are not using current-context
at all.
Miroslav Bajtoš
Edgars Zagorskis
Miroslav Bajtoš
biniam
Emiliano Daddario
josieusa
Simon Ho
Siddhi Pai
Amirali Jafarian
Carl Fürstenberg