TypeScript icon, indicating that this package has built-in type declarations

    2.0.6 • Public • Published


    Simple utility for context propagation within Javascript applications and libraries. Loosely based on the ideas behind React's context, allows you to achieve the same goals (and more) without actually using react. It allows you to keep reference for shared variables, and access them down in your function call even if not declared in the same scope.

    How Context Works?

    The way context works is quite simple. Creating a context initializes a closure with a context storage object. When you run your context call, it takes your values, and places them in the context storage object. When your function finishes running, the context is cleared.


    The reason the context is cleared after its run is so that items can't override one another. Assume you have two running the same async function twice, and it writes to the context, expecting to read the value somewhere down the line. Now you have two competing consumers of this single resource, and one eventually get the wrong value since they both read from and write to the same place.

    API Reference

    Context tries to mimic the behavior of Javascript scopes without actually being in the same scopes, and the API is built around context initialization, setting of values within the context and retrieving values.


    Context's default export, it creates a context singleton object that can later be referenced.

    // ctx.js
    import { createContext } from 'context';
    export default createContext(); // { run: ƒ, bind: ƒ, use: ƒ, useX: ƒ }

    createContext also accepts an initialization function that's run every time is called. It allows intercepting the context initialization and adding custom logic, or default values. The init function is passed the context object run was called with, and the parent context if it was called within a previously created context. The init function needs to return the desired context object.

    createContext((ctx, parentContext) => {
      if (parentContext === null) {
        // we're at the top level
        // so let's add a default cart object
        return Object.assign(ctx, {
          cart: [],
      // we're in a sub context, so we already have those default values.
      return ctx;


    Runs a callback function within the context. It takes an object referencing the data you want to store within your context, and a callback function to run.

    // myFunction.js
    import ctx from './ctx';
    import sayUsername from './sayUsername';
    function myFunction(username) {
      return{ username }, sayUsername);

    If run is called within a different run call, the context values will be merged when the callback is run. When we exit our callback, the context will be reset to the values it had before the call.

    use() and useX()

    These are the main ways to access the context within your code. They return the current object that stored within the context, and differ in the way they handle calls outside of the context.

    • use() returns the current object stored within the context, or null if we're not within a run call.
    • useX() returns the current object stored within the context, or throws an error if we're not within a run call.
      • useX also takes an optional argument that will be used as the error message if the context is not found.
    // sayUsername.js
    import ctx from './ctx';
    function sayUsername() {
      const context = ctx.use(); // { username: 'John Doe' }
      if (!context) {
        // we're not within a `run` call. This function was called outside of a running context.
        return "Hey, I don't know you, and this is crazy!";
      return `Hello, ${context.username}!`;
    // handleCart.js
    import ctx from './ctx';
    function handleCart() {
      const context = ctx.useX(
        'handleCart was called outside of a running context'
      ); // { cart: { items: [ 'foo', 'bar' ] } }
      // This throws an error if we're not within a `run` call.
      // You should catch this error and handle it somewhere above this function.
      return `You have ${context.cart.items.length} items in your cart.`;


    Bind a function to a context. It takes an object referencing the data you want to store within your context, and a callback function to run. It returns a function that can be called with the same arguments as the original function. The function will then internally call run with the same arguments, and return the result of the callback function, so it is useful if you want to reference a context after it was closed, for example - when running an async function.

    // getProductData.js
    import ctx from './ctx';
    function getProductData(productId) {
      return ctx.bind({ productId }, handleProductData);
      fetchProduct(productId).then(data => {
        // will run the function handleProductData within our context, even though there is no context running at the moment.


    Working with async functions/promises

    Working with context inside within async code may lead to unexpected results when we don't fully consider what's happening. Trying to call your context from the async part of your code will probably return null instead of your values.

    This is known and expected behavior. Context is a synchronous context propagation tool that completely relies on the synchronous nature of function calls in JS - this is exactly what allows context to run.

    But my function is still running. Why did the context clear?

    The async parts of your function are actually not executed along with your sync code, and even though you "await" it, the browser carries on and allows other code to run in between instead of blocking execution until your async code is complete.

    Ok, so what do I do?

    There are multiple strategies of handling async functions with context.

    1. Pulling your values from context right before your async call This is the most obvious and easiest to achieve, though not always what you need. The basic idea is that you take whatever you need from the context when it is still available to you.

    2. context.bind or your async function to the context you extracted This is the next logical step - you have a function that you know should run later with your context. You can bind your context to it for delayed execution. When your function runs later down the line within your asynchronous code, internally it will still have access to whatever you bound to it.




    npm i context

    DownloadsWeekly Downloads






    Unpacked Size

    22.1 kB

    Total Files


    Last publish


    • ealush