feat: add deep-equal-json

[SukkaW]

Closes #67.

A11yance/axobject-query#354

[valadaptive]

I'm not sure dequal is equivalent to deep-equal-json--for instance, I believe dequal traverses Maps and Sets whereas deep-equal-json uses referential equality

[SukkaW]

I'm not sure dequal is equivalent to deep-equal-json--for instance, I believe dequal traverses Maps and Sets whereas deep-equal-json uses referential equality

The reason behind the alias is that I don't want to re-implement deep equal over and over again. JS community has enough existing implementations on the npm.

Currently, the only dependent of the deep-equal-json is the axe project. What I am really afraid of is that ljharb spread his toxic dependencies even further, which could become a serious compat issue.

[SukkaW]

I'm not sure dequal is equivalent to deep-equal-json--for instance, I believe dequal traverses Maps and Sets whereas deep-equal-json uses referential equality

@valadaptive

It seems that deep-equal-json is only for JSON-supported values, so Map and Set might not be an issue since objects containing them should not be passed to deep-equal-json in the first place anyway.

On the other hand, should I use dequal/lite instead? It seems that dequal/lite also doesn't include deep Map and Set comparisons and thus behaves similarly.

[valadaptive]

It seems like dequal/lite is part of the dequal package already--I think that'd be preferable, yeah

[mikkurogue]

Currently, the only dependent of the deep-equal-json is the axe project. What I am really afraid of is that ljharb spread his toxic dependencies even further, which could become a serious compat issue.

Doing God's work ❤️

[SukkaW]

It seems like dequal/lite is part of the dequal package already

dequal is already lightweight enough, thus not a problem. The behavior match is more important in this context.