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 🙏

© 2026 – Pkg Stats / Ryan Hefner

update-set

v1.0.4

Published

`update-set` is a path-based setter for building update payloads.

Readme

update-set

update-set is a path-based setter for building update payloads.

Unlike lodash.set, it does not write the raw value to the leaf node. It always stores:

{ __set__: true, __value__: value }

This makes it possible to distinguish "this field was explicitly updated" from ordinary object data.

Install

npm install update-set

Usage

import set from 'update-set';

const target = {};

set(target, 'profile.name', 'Neo');

console.log(target);
// {
//   profile: {
//     name: {
//       __set__: true,
//       __value__: 'Neo'
//     }
//   }
// }

Path semantics

update-set treats dot paths and bracket index paths differently:

import set from 'update-set';

const objectPath = {};
set(objectPath, 'a.2.c', 'value');
// {
//   a: {
//     2: {
//       c: {
//         __set__: true,
//         __value__: 'value'
//       }
//     }
//   }
// }

const arrayPath = {};
set(arrayPath, 'a[2].c', 'value');
// {
//   a: [
//     undefined,
//     undefined,
//     {
//       c: {
//         __set__: true,
//         __value__: 'value'
//       }
//     }
//   ]
// }
  • a.2.c treats 2 as an object key.
  • a[2].c treats 2 as an array index.
  • Array-form paths are supported: set(target, ['items', 1, 'name'], 'Neo').

Nested updates on wrapped values

If a node has already been wrapped with __set__ and __value__, later nested updates continue inside __value__:

import set from 'update-set';

const target = {};

set(target, 'config', { enabled: false, name: 'demo' });
set(target, 'config.enabled', true);

console.log(target);
// {
//   config: {
//     __set__: true,
//     __value__: {
//       enabled: {
//         __set__: true,
//         __value__: true
//       },
//       name: 'demo'
//     }
//   }
// }

Notes

  • set(null, path, value) returns null and does nothing.
  • Quoted numeric bracket indices such as list["1"].done still work, but they log a deprecation warning. Prefer list[1].done.

API

declare function set<T extends object>(
  object: T,
  path: string | number | ReadonlyArray<string | number>,
  value: any,
): T;