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

wtdiff

v1.0.7

Published

Spanned from a problem I had at work while dealing with deciding what to send as part of the payload.

Downloads

4

Readme

WTDiff!

Spanned from a problem I had at work while dealing with deciding what to send as part of the payload.

Rule of thumb from experience, just send what's necessary to make the update.

Why?

KISS - Keep it simple and stupid

  1. We need to keep changes predictable
  2. Our consuming source does not need to know about what has not changed
  3. The consuming source should simply run the updates based on all the fields sent

Let's get to it

CommonJS

const wtdiff = require("wtdiff")

const dude1 = {name: "dude", job: "guitar player"}
const dude2 = {name: "dude", job: "developer"}

cosnt changes = wtdiff.extractChanges(dude1, dude2)

console.log(changes)
/**
  {
    job: "developer"
  }
*/

ES Modules

import wtdiff from 'wtdiff'

const dude1 = {name: "dude", job: "guitar player"}
const dude2 = {name: "dude", job: "developer"}

cosnt changes = wtdiff.extractChanges(dude1, dude2)

console.log(changes)
/**
  {
    job: "developer"
  }
*/

Supporting

  • [x] Nested objects
  • [] Nested arrays