evalir

Hi! I'd love to pick this up so we can get `ESM` going 😄 . Is there anything I should be aware of regarding this?

Alright! I'll pick this up in the following days 😃

Closing—already done

Fixed with https://github.com/foundry-rs/foundry/pull/5164 💆 see output: 

Alright, so after stubbing some things, here's the tasks. It's not 100% exhaustive as many of the seaport gossip functionalities in the reference implementation are still unfinished/unclear: - [ ]...

Right, i meant ssz encoding/decoding for the _seaport_ types we currently have, using ssz_derive. For JSON encoding, i'm just still unsure if they encode the types into a different json...

@igor-ritual this should be working now—could you do `foundryup` and confirm? if not i'll reopen and triage.

Yep I agree we could probably refactor `cast` a bit—we have to be careful about breaking changes around this though

So, I can confirm this is an issue—even though just fixing it could make everyone's CI or local runs _extremely_ noisy as a default. @mds1 this is somewhat easy fix,...

Wonder if we're now able to catch this with https://github.com/foundry-rs/foundry/pull/6530 cc @brockelmore