1.3.0 • Public • Published

Change Tracker

An object-focused alternative to Publisher / Subscriber models.

What's the purpose of this library?

To offer a simple means of tracking a variable's initialization and subsequent changes.

The variable you're tracking can be a primitive or an object. This library is not opinionated about the data types you use.


npm install change-tracker
import ChangeTracker from 'change-tracker';

// Init the tracker
const myTrackedObject = new ChangeTracker();

// Set a value. This may be done at any time. We track the parent object reference.
myTrackedObject.setValue({ name: 'John' });

// Log the value if already set; else, log it as soon as it's set.
myTrackedObject.getOnce(({ name }) => {
  console.log('-> [Logged once] Name:', name);

// Log the value every time it changes. Log immediately if it's already been set.
myTrackedObject.getEveryChange(({ name }) => {
  console.log('-> [Logged every time] Name:', name);

// Log the value next time it's set. Don't log if it's already been set.
myTrackedObject.getNext(({ name }) => {
  console.log('-> [Logged on next change] Name:', name);

// You can directly check the last known value. This is undefined if not yet
// set, else it contains the most recently set value.
console.log('Cached name:', myTrackedObject.cachedValue?.name);

Example use-case

We are making a 3D video game and need to keep track of a spaceship. Game boot is asynchronous and spaceship load time cannot be determined. Additionally, some parts of our game need to be notified when the player switches to a different spaceship. To complicate matters, our main game loop runs at 60 frames per second from early on and cannot use asynchronous callbacks, but needs to render the ship as soon as it's ready.

Let's assume we have a spaceship class for loading our 3D spaceship. For the sake of demonstration, we'll define our ship as:

class PlayerShip {
  constructor() { console.log('New ship loaded.'); }
  get name() { return 'Friday'; }
  render() { /* do gfx magic */ }

Let's write some code to track our game objects:

// core.js

import ChangeTracker from 'change-tracker';

const gameObjects = {
  playerShipTracker: new ChangeTracker(),

export {
// shipLoader.js

// Create the spaceship:
gameObjects.playerShipTracker.setValue(new PlayerShip());
// ^^ message is logged: 'New ship loaded.'

On first init, welcome the player:

// boot.js

// This is called only after initialization. If the player ship has already
// been initialized, it'll call back immediately.
gameObjects.playerShipTracker.getOnce((shipInstance) => {
  alert('Welcome to The Space Game!');
  console.log('Player loaded',;

Every time the ship is loaded (including init), update the UI:

// ui.js

gameObjects.playerShipTracker.getEveryChange((shipInstance) => {
  const shipNameDiv = document.getElementById('ship-name');
  if (shipNameDiv) {
    shipNameDiv.innerHTML =;

From very early on, our GFX engine renders anything that can be rendered. It should render the ship as soon as it's loaded, but cannot use delayed callbacks for obvious timing reasons (it would queue a new callback 60 times a second, indefinitely, and then eventually have thousands of old requests trigger at once). Instead of keeping track of boot manually, you can get the latest known value of the ship. It will be undefined until the spaceship has loaded. Thereafter, we'll have a valid value.

function renderGame() {
  const ship = gameObjects.playerShipTracker.cachedValue;
  if (ship) {

Better IDE completion

If you want better IDE autocompletion, you can instead use TypeScript in the initial definition. Here's an example of how you could rewrite the definition in the first example code block:

interface TrackedPlayerShip extends ChangeTracker { cachedValue: PlayerShip; }

const playerShipTracker: TrackedPlayerShip = new ChangeTracker();

const gameObjects = { playerShipTracker };

// gameObjects.playerShipTracker.cachedValue.<< auto-completes properties >>

Note that your transpiler will already need to be set up to take advantage of this. For reference, the config we used to build Change Tracker can be found here.


This library supports all modern browsers, and Node.js (with your choice of import or require).

You may install the library like so:

npm install change-tracker


const ChangeTracker = require('change-tracker');

Browsers and modern Node.js:

import ChangeTracker from 'change-tracker';

For browsers, it is recommended you use a bundler like Webpack. If you insist on using the library in a browser without a bundler, you can source it from a CDN such UNPKG which will store the main class in window scope:

<script src="^1/browser.js"></script>
  const myVar = new ChangeTracker();


All functions are annotated with JSDoc comments so that your IDE can feed you manuals on the fly (triggered by Ctrl+Q in IntelliJ, for example).


  • Initialization:
import ChangeTracker from 'change-tracker';
const trackedValue = new ChangeTracker();
  • Set the value, and inform all subscribed listeners that the value has changed:
  name: 'Joe',
  • You can request to be notified next time the variable changes, or is initialized for the first time. If the value has already been initialized, then getOnce will be triggered immediately:
trackedValue.getOnce((trackedValue) => {
  console.log('Value has changed to:', trackedValue);
  console.log('This function will not be notified again.');
  • You can undo a getOnce that has not yet been triggered, so long as you keep a reference to the original function:
function onValueChange(trackedValue) {
  console.log('Value has changed to:', trackedValue);
  console.log('This function will not be notified again.');

  • Subscribe to all changes indefinitely, then unsubscribe:
function onValueChange(trackedValue) {
  console.log('Value has changed to:', trackedValue);


// [...]

  • Get the next change only:
function onValueChange(trackedValue) {
  console.log('Value has changed to:', trackedValue);


// ...or undo that decision:
  • Get notified until the coin lands tails:
console.log('Flip until we get tails.');

function onValueChange(coinSide) {
  if (coinSide < 0.5) {
    console.log('-> tails.');
    // Subscription terminates.
  else {
    console.log('-> heads.');


// Flip coin forever:
setInterval(() => {
}, 500);
  • In some cases, you may want to wait for multiple trackers to resolve, similar to how Promise.all() functions. ChangeTracker has a static function named ChangeTracker.waitForAll() which serves this purpose. It returns a ChangeTracker instance for you to watch. Example:
const resolvesQuickly = new ChangeTracker();
const resolvesSlowly = new ChangeTracker();

]).getOnce(() => {
  console.log('All trackers resolved.');

setTimeout(() => resolvesQuickly.setValue(1), 10);
setTimeout(() => resolvesSlowly.setValue(1), 5000);
  • For special requirements where delayed callbacks are not appropriate, you can read the latest value directly:
console.log('-> Value:', trackedValue.cachedValue);
// ^^ undefined if not yet set, otherwise the currently held value.

Edge-case functions

  • In almost all cases, you should use setValue() to change the stored value as this rightfully notifies all listeners who need to know of the change. If you feel you have a very good reason to bypass notifying all listeners, and you're sure the bypass won't mess up state in your application, you can set the value and suppress notifications with:
trackedValue.setSilent('This value is not be propagated.');


This package has no production dependencies, though it does use Babel for transpilation and Webpack for bundling. If you dislike this, you can import the actual zero-dependency code as is using:

import ChangeTracker from 'change-tracker/src/index.ts';

Note however that this method requires a transpiler with TypeScript support (you may look at our webpack config to see how we did it).

Why is this repo not being updated?

If we've done our job correctly, there shouldn't be many updates. This library is meant to be simple yet powerful, and leaves design details up to you.

We'll update it to support modern tech changes as needed.

Other examples

On document ready

Miss jQuery's clean $(() => console.log('document ready!')) function but refuse to use jQuery?

A quick and dirty implementation might look something like this:

const docReadyTracker = new ChangeTracker();
window.$ = onReady => docReadyTracker.getOnce(onReady);
window.onload = event => docReadyTracker.setValue(event);

You can now utilize this elsewhere as follows:

$(() => console.log('document ready!'))

This custom on-ready function may be called at any time.


npm i change-tracker

DownloadsWeekly Downloads






Unpacked Size

50.3 kB

Total Files


Last publish


  • frostoven