What is the key feature we're aiming to implement?

wasm32v1-none is relatively new, and the main difference from wasm32-unknown-unknown is no std support at all (whilst, in wasm32-unknown-unknown, there still is some std support).

The problem is, some of our utility crates like event-assertion and default-impl-macro-test are using std code, and with a cfg flag, they are not compiled for wasm32 targets.

However, since the entire crate is discarded for wasm32 targets, it seems cargo is filling the empty crate with some std::prelude stuff, which is supported by wasm32-unkown-unkown but not by wasm32v1-none.

In the future, we may get rid of default-impl-macro-test crate for good.

But, still, we should think of an ergonomic solution for event-assertion crate for wasm32v1-none target.