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

tfg-event-context

v1.0.1

Published

Universal Event context for JavaScript

Downloads

307

Readme

event-context

  • Work only with NodeJS
  • No dependencies

Features

  1. automatic state passing to downstream functions without explicitly declaring them in functions' parameters (think of React's context but with inheritance). State values are accessible everywhere with ctx.getState()
  2. automatic disposal for every pending tasks and event listeners to prevent memory leaks. EventContext works with Promise as well, so you can abort nested unresolved promises with ease. Context disposal is accessible everywhere with ctx.dispose()

Plugins

EventContext for NodeJS (nextTick, EventEmitter) https://www.npmjs.com/package/tfg-event-context-plugin-node

Installation:

npm i -S tfg-event-context

# to use it with a plugin, just add the plugin package
npm i -S tfg-event-context-plugin-node

Usages

Passing data across functions without declaring them each time.

This is super useful to getting the request that causing an unexpected error. See the example below, it was not easy to get the req inside a downstream function without explicitly passing the req along the way.

import { withContext, getCurrentContext } from 'tfg-event-context';
import { patch } from 'tfg-event-context-plugin-node';

// patch all NodeJS binding after this call
patch();

const server = http.createServer(withContext((req, res) => {
  const ctx = getCurrentContext();
  const state = ctx.getState();

  state.req = req;

  handleRequest(req.path, (err, value) => {
    res.end(value);
  });
}));

function handleRequest(path, callback) {
  // do some works with path
  process.nextTick(() => {
    callDB(callback);
  });
}

function callDB(callback) {
  try {
    somethingWrong();
  } catch (ex) {
    const ctx = currentContext();
    const { req } = ctx.getState();
    const { method, url } = req;
    console.error('Server Error. Gracefully dying. Request causing error: ', method, url);
  }
}

State inheritance

State values are prototypically inherited (think of angular1's scope).


// initiate contexts
const parent = createContext('parent');
const child = createContext('child');

const pState = parent.getState();
const cState = child.getState();

// state can be set even before running.
pState.parentOnly = 'parentOnly';
pState.shared = 'parentShared';

cState.childOnly = 'childOnly';
cState.shared = 'childOverwrite';

const childComputation = () => setTimeout(() => {
  // child
  const state = getCurrentContext().getState();
  expect(state.childOnly).equal('childOnly');
  expect(state.parentOnly).equal('parentOnly');
  expect(state.shared).equal('childOverwrite');
  done();
}, 10);

const parentComputaion = () => setTimeout(() => {
  // parent
  child.run(() => {
    // child
    childComputation()
  })
}, 10)

parent.run(() => {
  // parent
  parentComputaion();
});

Contributions

All contributions are super welcome