Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
continuation-local-storage
Advanced tools
continuation-local-storage - npm Package Versions
Changelog
v3.0.0 (2013-12-14):
- Removed the notion of a "default" or "global" context per namespace. It only existed to create a simpler interface for developing and testing the module, and created the potential for nasty information disclosure bugs (see issue #14 for details). This is potentially a breaking change, if you're depending on the global context, so semver says we have to bump the major version.
- Added this changelog.
Changelog
v2.6.1 (2013-11-29):
emitter-listenerhas been extracted fromshimmerinto a standalone module fornamespace.bindEmitter().
Changelog
v2.6.0 (2013-11-27):
- When an error is thrown in a CLS-bound continuation chain, attach the active context for the namespace to which the chain is bound. This is necessary because CLS and asyncListeners actually do too good a job of cleaning up after errors, and so they don't escape the continuation chain. New Relic needs the context so it can get the transaction active when the error happened for error tracing.
Changelog
v2.5.2 (2013-10-30):
async-listenerdependency refresh for better support of node 0.8.0 - 0.8.3.
Changelog
v2.5.0 (2013-10-27):
- Relax the requirement that CLS contexts be pushed and popped from a stack,
instead treating them as a set. This allows context interleaving (i.e.
using the lower-level
namespace.enter()andnamespace.exit()API without any strict ordering dependencies). Everything works, but this still makes me a little uneasy. - EEs can now be bound to multiple namespaces, although this is likely to be slow.
Changelog
v2.4.4 (2013-10-27):
- Even if you use an EE bound to a namespace outside a continuation chain, it shouldn't explode.