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

object-history-debugger

v0.5.1

Published

See where the properties of an object were assigned and what their past values were.

Downloads

16

Readme

Object History Debugger CircleCI

See where an object's property values were assigned, plus a history of past values.

Demo Page

Setup

Add a plugin to your babel build

  1. npm install object-history-debugger
  2. Add object-history-debugger/babel-plugin to your Babel plugins, e.g. in .babelrc
  3. Put import ohd from "object-history-debugger" before any of your own JS code.
  4. Make sure your build has source maps enabled, if you want to use prettyPrint
  5. Build your project and load it as usual. Objects now have history values for each property.

Pretty printing the history currently only works in Chrome.

If you're excluding paths from your Babel build (e.g. the node_modules folder) assignments in those files won't be tracked.

Chrome extension: easy setup, but flaky

Install the Chrome extension then click the icon next to the URL bar to reload the current page with object tracking enabled.

The Chrome extension is quite hacky and some pages will break when Object History Debugger is activated.

Usage

You can either inspect the property's history in a debugger or call prettyPrint on the history property.

For example, if your property name is sth you would call obj.sth__history__.prettyPrint().

Pretty print shows you the original source code you wrote. Because it's asynchronous it won't log the history right away if you're paused in the debugger.

To see the history without having to resume execution call prettyPrintSynchronously.

Tracking only specific objects to save memory

Tracking all past property values can use up a lot of memory. Chrome can't garbage collect values if they are still referenced in a __history__ value.

To only track assignments on certain objects set trackAllObjects to false:

import ohd from "object-history-debugger"
ohd.trackAllObjects = false;

Then, to track assignments on obj:

ohd.trackObject(obj)