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-immutable-set

v1.0.0

Published

Immutably update an object

Downloads

219

Readme

object-immutable-set

npm version CircleCI

Updated deeply nested objects in an immutable and type-safe way. Written and providing first class support for Typescript

Usage

yarn add object-immutable-set

or using npm

npm install object-immutable-set --save

import { set } from 'object-immutable-set'

type ComplexObjectType = {
  a: number,
  b: {
    c: {
      d: {
        deepProperty: string,
        deeper: {
          otherProperty: Array<number>,
        },
      },
    },
  },
}

const deeplyNestedObject: ComplexObjectType = {
  a: 1,
  b: {
    c: {
      d: {
        deepProperty: 'original value',
        deeper: {
          otherProperty: [1, 2, 3],
        },
      },
    },
  },
}

const updatedObject: ComplexObjectType = set(deeplyNestedObject, ['b', 'c', 'd', 'deepProperty'], 'updated value')

updatedObject.b.c.d.deepProperty // 'updated value'
deeplyNestedObject.b.c.d.deepProperty // 'original value'
updatedObject.b.c.d.deeper === deeplyNestedObject.b.c.d.deeper // true 

Note that the second parameter is type safe meaning that if you attempted to do something like:

const updatedObject: ComplexObjectType = set(deeplyNestedObject, ['b', 'oops', 'd', 'deepProperty'], 'updated value')

you will get a compilation error similar to:

error TS2345: Argument of type '["b", "oops", "d", "deepProperty"]' is not assignable to parameter of type '["b", "c", "d", "deepProperty", "length" | ...'.
  
86     const updatedObject: ComplexObjectType = set(deeplyNestedObject, ['b', 'oops', 'd', 'deepProperty'], 'updated value')
                                                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Motivation

Sometimes you want to immutably update a deeply nested property, currently you are faced with either

  • losing type safety using an existing javascript-only / non-typesafe option e.g _.set or object-path-immutable
  • creating a deep clone and mutating it which can be expensive, and additionally will fail to re-use any of the previous object:
import { cloneDeep } from 'lodash'

const updatedObject = cloneDeep(originalObject)
updatedObject.a.b.c.d = 'This was a bit expensive'
  • lots of error-prone boilerplate
const updatedObj = {
  ...originalObject,
  a: {
    ...originalObject.a,
    b: {
      ...originalObject.a.b,
      c: {
        ...originalObject.a.b.c,
        d: 'You can see where this is going'
      },
    },
  },
}

We found this to be particularly useful when working with React component state or, less often, a complex Redux reducer.

Contributing

Pull requests and issues welcome and encouraged!

Before submitting a PR please make sure that you:

  • Check that everything compiles: yarn lint
  • Run the tests: yarn test adding new tests to preserve the code coverage
  • Run the linter: yarn lint to make sure new code conforms to the existing style