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 🙏

© 2024 – Pkg Stats / Ryan Hefner

thread-context

v0.1.1

Published

"Thread context" emulation for Node.js based on continuation local storage

Downloads

480

Readme

thread-context

This module is located at https://github.com/Aggtaa/thread-context. Any other location is either a fork or a copy.

Overview

This module helps to mitigate absense of "thread context" in node.js, where threads are missing. It utilizes cls-hooked to access continuation local storage and provides a thin yet convenient wrapper around it. It allows you to store data once and access it from any subsequent synchronous or asynchronous function call. Call stack from an express handler where every request can is given a unique ID makes a good example.

API

The usage is straightforward:

The threadContext object that can be imported from the thread-context module, is a Proxy object with virtual getter and setter and implements undefined type (for those of you using typescript). It allows storing data of any structure within one stack call ("thread")

You simply call threadContext.init() once in the topmost function of a callstack (e.g. an express handler), giving a context a unique id. The id is later available as threadContext.threadId.

Any read or write to threadContext fields yields same result within one "thread" no matter how deep in call stack execution is.

The threadContext "threads" are disposed automatically, there is nothing you need to do.

Example

index.js

import debug from 'debug';
import express from 'express';
import { threadContext } from 'thread-context';
import { generateThreadReport } from './report';
import { generateSuperUniqueId } from './uniqueIdGenerator';

const app = new express.Express();

app.use(async (req, res, next) => {
    
    // start a threadContext and give it a unique ID
    await threadContext.init(generateSuperUniqueId());
    // or simply threadContext.init();

    // store some data for later
    threadContext.requestMethod = req.method;
    threadContext.requestPath = req.originalPath;

    debug.log(`[${threadContext.threadId}] ${threadContext.requestMethod} ${threadContext.requestPath}: threadContext init`);

    next();
});

app.get('/thread.json', (req, res, next) => {
    res.json(generate);
});

app.get('/someOtherUrl', (req, res, next) => {
    debug.log(`[${threadContext.threadId}] ${threadContext.requestMethod} ${threadContext.requestPath}: still in same threadContext`);
    // ...
    res.end();
});

report.js

import debug from 'debug';
import { threadContext as ctx } from 'thread-context';

export function generateThreadReport() {

    debug.log(`[${ctx.threadId}] ${ctx.requestMethod} ${ctx.requestPath}: generating report`);

    return {
        threadId: ctx.threadId,
        requestMethod: ctx.requestMethod,
        requestPath: ctx.requestPath,
    }
}