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

@ctx/context

v1.2.0

Published

[![Build Status](https://travis-ci.org/node-context/context.svg?branch=master)](https://travis-ci.org/node-context/context) [![Dependency Status](https://gemnasium.com/badges/github.com/node-context/context.svg)](https://gemnasium.com/github.com/node-cont

Downloads

61

Readme

Context

Build Status Dependency Status

Go's context package, reimplemented in Typescript. Carry timeouts, cancellations and arbitrary values through the entirety of your stack.

Installation

yarn add @ctx/context

Usage

This module defines the Context type, which carries deadlines, cancelation signals, and other request-scoped values across API boundaries and between processes.

Incoming requests to a server should create a Context, and outgoing calls to servers should accept a Context. The chain of function calls between them must propagate the Context, optionally replacing it with a derived Context created using WithCancel, WithDeadline, WithTimeout, or WithValue. When a Context is canceled, all Contexts derived from it are also canceled.

The WithCancel, WithDeadline, and WithTimeout functions take a Context (the parent) and return a derived Context (the child) and a CancelFunc. Calling the CancelFunc cancels the child and its children, removes the parent's reference to the child, and stops any associated timers. Failing to call the CancelFunc leaks the child and its children until the parent is canceled or the timer fires.

Programs that use Contexts should follow these rules to keep interfaces consistent across packages and enable static analysis tools to check context propagation:

Do not store Contexts inside classes and objects; instead, pass a Context explicitly to each function that needs it. The Context should be the first parameter, typically named ctx:

function DoSomething(ctx: context.Context, arg: any) {
	// ... use ctx ...
}

Do not pass an undefined Context, even if a function permits it. Pass context.TODO if you are unsure about which Context to use.

Use context Values only for request-scoped data that transits processes and APIs, not for passing optional parameters to functions.

See https://blog.golang.org/context for example code for a server that uses Contexts.

Examples

Creating a context from an incoming request, and setting a timeout

This example is implemented by @ctx/express

const app = express()
app.use((req, res, next) => {
    // Set up a context
    if (!req.ctx) {
        req.ctx = context.Backgrond()
    }
    // Add a request id, or pass through an existing request id
    if (!req.ctx.Value('request-id')) {
        let cancel
        [req.ctx, cancel] = context.WithValue(req.ctx, 'request-id', new uuid())
        res.on('finish', () => cancel)
    }
    // Set a timeout for the request
    let cancel
    [req.ctx, cancel] = context.WithTimeout(req.ctx, 1000)
    res.on('finish', () => cancel)

    next()
})