Creating all objects without prototypes breaks public API

[nerdbeere]

Hi @BinaryMuse

one could argue that the changes introduced in 7f84702 are changing the public api of your module and following semver should lead to a new major version instead of the patch version you published.

I use nconf in combination with your package which unfortunately relies on Object.hasOwnProperty which no longer works.

[kosmasgiannis]

See also indexzero/nconf#314

[BinaryMuse]

@nerdbeere You're right - sorry about this. I didn't consider it until after it was published to npm, and I sort of waffled on whether or not it would be a breaking change.

I'm thinking of reverting this change, publishing a new 2.x release, and then re-committing the fix in a new 3.x line. Do you have any other ideas?

[nerdbeere]

@BinaryMuse Sounds like a good strategy to me.

[BinaryMuse]

This change is reverted in v2.3.6 and has been reapplied for v3.0.0.