零Rei

This seems to still be busted as of Node 9 -- is there something we need to do to address this in either `async-listener` or CLS?

Why is this PR necessary? The current semver range (`async-listener@^0.6.0`) will automatically pick up `[email protected]` upon a fresh install. Is there a particular reason to pin the dependency?

What's the use case behind this? In principle, I have no objection, but I'd like to understand what you're trying to do. Also, before this gets merged, it'll need tests...

- What version of Express? - What version of Node? - What's the setup code for `ns`? - How are you requiring `continuation-local-storage`? (i.e. where in the file / your...

Pretty sure that @arthurschreiber has it, although there may be some fancy continuation stuff that Express 4 is doing differently from Express 3 / Connect 2 and earlier. I'm sorry...

Patching Promise was introduced by @hayes. @trevnorris's core API preceded landing ES Promises in V8 (and the concomitant challenge of handling the new microtask queue).

I would love to see CLS brought up to date with modern versions of Node. `async_hooks` is on its way out of being experimental, so the time is right to...

I would be happy to bless a solution put together by others, or accept a patch to add a browser-side solution that either gets full CLS running or creates enough...

The CLS bits are easy. It's creating an `async-listener`-like substrate for the browser that's tricky.

I still don't have a good solution for this from within CLS, but I'd point out that [Angular's Zones](https://github.com/angular/zone.js/) are apparently in the early stages of TC39 standardization. Hope you...