structural clone support

[jimmywarting]

Hi, i added yours to this list of test: https://jimmywarting.github.io/3th-party-structured-clone-wpt/
wanted to run benchmark as well. but it's blocked by #1 for some json

[vipertechofficial]

@jimmywarting Hi, take a look at the V3.0 it should be OK

[jimmywarting]

it was running Okey now.
but i can leave this open if you want to improve the overall structural clone support for other kind of data. or you can close this if you want to.

[vipertechofficial]

Yes sure thanks

[vipertechofficial]

@jimmywarting I am inclined into putting my mind into work to improve superjsonatural, maybe you may want as you are a fine in-depth expert in testing those serializer them all, willing to guide this project's update with requirement, I would like to beat messagepkr

Edit: I may warn that my idea is potentially useless as https://www.npmjs.com/package/sializer could be somehow what could be the solution I am referring to, could you add "sializer" to your page ?

[jimmywarting]

sializer have been added.
one thing i like about cbor-x is is that it is based upon the CBOR specification. in fact that is also what chrome uses for some serialization like in indexeddb, webauthn and the payment api.
indexeddb also use the structuralClone algoritm so it wouldn't chock me if it too was based upon cbor.

there have also been talks about exposing structuralClone and/or cbor natively: whatwg/html#3517

if you want to beet other serializer, try to increase the overall score on my testing website and try to support everything structuralClone can support