Question

json2.js seems to ignore members of the parent object when using JSON.stringify(). Example:

require('./json2.js');

function WorldObject(type) {    
    this.position = 4;
}

function Actor(val) {
    this.someVal = 50;
}

Actor.prototype = new WorldObject();

var a = new Actor(2);

console.log(a.position);
console.log(JSON.stringify(a));

The output is:

4
{"someVal":50}

I would expect this output:

4
{"position":0, "someVal":50}

Answer 1

Well that’s just the way it is, JSON.stringify does not preserve any of the not-owned properties of the object. You can have a look at an interesting discussion about other drawbacks and possible workarounds here.

Also note that the author has not only documented the problems, but also written a library called HydrateJS that might help you.

The problem is a little bit deeper than it seems at the first sight. Even if a would really stringify to {"position":0, "someVal":50}, then parsing it later would create an object that has the desired properties, but is neither an instance of Actor, nor has it a prototype link to the WorldObject (after all, the parse method doesn’t have this info, so it can’t possibly restore it that way).

To preserve the prototype chain, clever tricks are necessary (like those used in HydrateJS). If this is not what you are aiming for, maybe you just need to “flatten” the object before stringifying it. To do that, you could e.g. iterate all the properties of the object, regardless of whether they are own or not and re-assign them (this will ensure they get defined on the object itself instead of just inherited from the prototype).

function flatten(obj) {
    var result = Object.create(obj);
    for(var key in result) {
        result[key] = result[key];
    }
    return result;
}

The way the function is written it doesn’t mutate the original object. So using

console.log(JSON.stringify(flatten(a)));

you’ll get the output you want and a will stay the same.