npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

cls-tls

v0.1.0

Published

make node tls socket client work with cls (continuation-local-storage)

Readme

cls-tls

When using cls continuation-local-storage with a node tls client socket, the cls contexts get lost in some client socket event callbacks (such as write callback) and tls.connect event, for example,

var tls = require('tls');
var cls = require('continuation-local-storage');
var ns = cls.createNamespace('test');

ns.run(function () {
    ns.set('id', '1');
    var tlsSocket = tls.connect(8000, 'localhost', options, function () {
        tlsSocket.write('hello node!', 'utf8', function () {
            var id = ns.get('id');
            assert.ok(id); // this throws AssertionError
        });
    });
});

This shim cls-tls monkeypatches the node tls module and/or tls.TLSSocket socket instances. The goal is to make tls socket client work with cls namespace/context.

Usage example - if you create tls socket using "tls.connect"

If you are using convenient tls module api "tls.connect" to make tls connection, use this shim api 'patchTls(ns)'. Calling this api patches the tls module method tls.connect so it works with cls namespace/context, the tls socket created as result of calling tls.connect is also patched so it works with cls namespace/context.

An example,

var tls = require('tls');
var cls = require('continuation-local-storage');
var ns = cls.createNamespace('test');

var { patchTls } = require('cls-tls');
patchTls(ns);

ns.run(function () {
  ns.set('id', '1');
  var tlsSocket = tls.connect(8000, 'localhost', options, function () {
    tlsSocket.write('hello node!', 'utf8', function () {
      var id = ns.get('id');
      assert.equal(id, '1'); // pass
    });
  });
});

Usage example - if you create tls socket using "new tls.TLSSocket"

If you are creating tls.TLSSocket instance using "new tls.TLSSocket" to make tls connection, use this shim api 'patchTls(ns, tlsSocket)'. Calling this api patches the passed-in tls socket
so it works with cls namespace/context.

An example,

var tls = require('tls');
var cls = require('continuation-local-storage');
var ns = cls.createNamespace('test');

var { patchTls } = require('cls-tls');

ns.run(function () {
  ns.set('id', '1');
  
  var tlsOptions = {...};
  var tlsSocket = new tls.TLSSocket(undefined, tlsOptions);
  
  patchTls(ns, tlsSocket); // patching this single pre-allocated tls client socket
  
  tlsSocket.connect({ port: 8000, host: 'localhost' });
  
  tlsSocket.write('hello node!', 'utf8', function () {
    var id = ns.get('id');
    assert.equal(id, '1'); // pass
  });
});

For more formal examples, please see test/*.tap.js files.

Tests

Run

$ npm test

Before running the tests, you must run a TLS socket server via

$ node test/TlsServer.js

Note: the server key and cert files under /test were generated before (running above TLS server) using

$ openssl genrsa -out server-key.pem 4096
$ openssl req -new -key server-key.pem -out server-csr.pem
$ openssl x509 -req -in server-csr.pem -signkey server-key.pem -out server-cert.pem