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

dynamic-context

v1.1.0

Published

Dynamic context manages your mutation stack allowing your application to easily share context in an idempotent way

Downloads

6

Readme

dynamic-context

Dynamic context manages your mutation stack allowing your application to easily share context in an idempotent way.

What does that actually mean?

When you change an individual value, an entirely new context is created - all of the original values are copied forward and only the new value is actually changed.

> npm install -S dynamic-context
const _context = require('dynamic-context');

const homer = _context(['firstName', 'lastName']).lastName('Simpson').firstName('Homer');
const marge = homer.firstname('Marge');

console.log(`${homer.firstName()} ${homer.lastName()}`);
// Homer Simpson
console.log(`${marge.firstName()} ${marge.lastName()}`);
// Marge Simpson

Values can also be changed via a setter, which allows you to clear a value that you've previously defined.

const _context = require('dynamic-context');

const homer = _context(['firstName', 'lastName']).lastName('Simpson').firstName('Homer');
const marge = homer.set('firstName', 'Marge');
const unknown = homer.set('firstName');

console.log(`${homer.firstName()} ${homer.lastName()}`);
// Homer Simpson
console.log(`${marge.firstName()} ${marge.lastName()}`);
// Marge Simpson
console.log(`${unknown.firstName()} ${unknown.lastName()}`);
// undefined Simpson

You can also access the parent context which allows you to traverse up the context tree.

const _context = require('dynamic-context');

const homer = _context(['firstName', 'lastName', 'relation']).lastName('Simpson').firstName('Homer');
const bart = homer.relation('son').firstName('Bart');
const lisa = homer.relation('daughter').firstName('Lisa');

console.log(`${bart.firstName()} ${bart.lastName()} ${bart.relation()} of ${bart.parent().firstName()}`);
// Bart Simpson son of Homer
console.log(`${lisa.firstName()} ${lisa.lastName()} ${lisa.relation()} of ${lisa.parent().firstName()}`);
// Lisa Simpson daughter of Homer

Whilst individual values are idempotent, they are subject to the same variability as all other javascript objects.

const _context = require('dynamic-context');

const obj = {
  firstName: 'Homer',
  lastName: 'Simpson'
}

const homer = _context(['person']).person(obj);
obj.firstName = 'Marge';

console.log(`${homer.person().firstName} ${homer.person().lastName}`);
// Marge Simpson <<-- notice that the name may not be what you expected