Test and use native structuredClone if it exists.

[jdalton]

Native structuredClone is landing in browsers. It would be great if this forked to use that if it exists.

[dumbmatter]

That is a good point. I might wait until Node.js does a release including it, since this library is mostly used in Node.js and that would give me a chance to make sure nothing funny happens with the switch.

[dumbmatter]

Wow things happen fast. structuredClone is in the latest version of Node. It actually fails one of the tests here, since now Error objects are structured clonable but that was not always true.

But thinking about this issue again... is it actually better for this library to handle if we can use the native structuredClone, or would it be better to let the application decide? I feel like letting the application decide is the least confusing way? I guess it probably matters for very few people, since basically everyone using this library is using it as a dependency of another library I wrote (fake-indexeddb), so everyone using that will get the change regardless of if I make it here or there :)