I\'ve not seen (yet?) JSON.stringify
to be non-deterministic in Node.JS.
There is no guarantee it to be deterministic on the specification level.
To clarify jmrk's answer;
According to the spec, integer keys are serialized in numeric order and non-integer keys in chronological order of property creation, e.g.;
var o = {};
o[2] = 2;
o.a = 3;
o.b = 4;
o["1"] = 1;
assert(JSON.stringify(o)==='{"1":1,"2":2,"a":3,"b":4}');
Therefore following assertion is guaranteed to be true
if( obj1 === obj2 ) {
assert(JSON.stringify(obj1) === JSON.stringify(obj2));
}
but two "deep equal" objects may be serialized into different strings;
var obj1 = {};
obj1["a"] = true;
obj1["b"] = true;
assert(JSON.stringify(obj1)==='{"a":true,"b":true}');
var obj2 = {};
obj2["b"] = true;
obj2["a"] = true;
assert(JSON.stringify(obj2)==='{"b":true,"a":true}');
Spec quote;
- Let keys be a new empty List.
For each own property key P of O that is an integer index, in ascending numeric index order, do
a. Add P as the last element of keys.
For each own property key P of O that is a String but is not an integer index, in ascending chronological order of property creation, do
a. Add P as the last element of keys.
For each own property key P of O that is a Symbol, in ascending chronological order of property creation, do
a. Add P as the last element of keys.
- Return keys.
From https://tc39.github.io/ecma262/#sec-ordinaryownpropertykeys
Determinism in your terms boil down to these:
Yes, the traversal through the object data happen in the same 'route' always.
Yes, unless the arbitrariness introduced through toJSON overrides as @jmrk explained above.
No, V8 script runner is single threaded, so no cluttered access happen.
No, apart from the contextual replacers / overrides, the parser and stringify SHOULD produce same data everytime.
No, the spec is not clear on the order of listing Object fields so implementations are free to iterate through objects which means the data may be same to the 'purpose' and 'spirit', not comparable byte-to-byte.
Hope this helps!
If by "deterministic" you mean enumeration order of the object's properties: that is actually specified, and V8 follows the spec. See https://tc39.github.io/ecma262/#sec-ordinaryownpropertykeys. [Edit: this is the answer to your clarified definition, so yes, JSON.stringify is deterministic in that sense.]
If by "deterministic" you mean "always returns the same string for the same input object", then, well, no :-)
> var o = { toJSON: function() { return Math.random(); } }
> JSON.stringify(o);
< "0.37377773963616434"
> JSON.stringify(o);
< "0.8877065604993732"
Proxy
objects and the replacer
argument to JSON.stringify
can also be used to create arbitrary behavior (even though JSON.stringify
itself always does the same thing).
If by "deterministic" you mean something else, please specify.
In case anyone would look for a function that'll make the JSON dump predictable, I wrote one:
const sortObj = (obj) => (
obj === null || typeof obj !== 'object'
? obj
: Array.isArray(obj)
? obj.map(sortObj)
: Object.assign({},
...Object.entries(obj)
.sort(([keyA], [keyB]) => keyA.localeCompare(keyB))
.map(([k, v]) => ({ [k]: sortObj(v) }),
))
);
Here's a composed deterministic JSON dump:
const deterministicStrigify = obj => JSON.stringify(deterministic(sortObj))
It works well with the examples above:
> obj1 = {};
> obj1.b = 5;
> obj1.a = 15;
> obj2 = {};
> obj2.a = 15;
> obj2.b = 5;
> deterministicStrigify(obj1)
'{"a":15,"b":5}'
> deterministicStrigify(obj2)
'{"a":15,"b":5}'
> JSON.stringify(obj1)
'{"b":5,"a":15}'
> JSON.stringify(obj2)
'{"a":15,"b":5}'