Question 1

How do I escape a dot in a property name with set-value?

Accepted Answer

Prefix the dot with a backslash, like 'a\.b.c'. This prevents set-value from splitting on that dot, allowing properties with dots in their names. For example, set({}, 'a\.b.c', 'd') creates { 'a.b': { c: 'd' } }.

Question 2

set-value vs lodash.set: which is better for performance?

Accepted Answer

set-value consistently outperforms lodash.set in benchmarks, as shown in the README, and handles more edge cases correctly. However, lodash.set is part of the larger Lodash ecosystem, which might be preferable if you need additional utilities.

Question 3

Can set-value merge objects deeply instead of just overwriting?

Accepted Answer

Yes, by setting the merge option to true, it performs a shallow merge using Object.assign. For deep merging, you must provide a custom merge function, which requires extra implementation effort.

Question 4

Does set-value work with arrays or only objects?

Accepted Answer

set-value is designed for objects, but it can set properties on arrays if the path targets array indices. However, it doesn't provide specialized array manipulation features, so other libraries might be better for array-specific tasks.

Question 5

How to use a custom separator like slash in set-value?

Accepted Answer

Pass an options object with the separator property, e.g., set(obj, 'auth/user', 'value', { separator: '/' }). This splits the path on slashes instead of dots, useful for formats like file paths or URLs.

Question 6

Is set-value immutable or does it change the original object?

Accepted Answer

set-value mutates the original object. If you need immutable updates, you should first clone the object using methods like JSON.parse(JSON.stringify(obj)) or use a library designed for immutability.

set-value

What is set-value?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions