NyxCode

[#49359](https://github.com/rust-lang/rust/issues/49359) seems [kinda close](https://internals.rust-lang.org/t/path-for-stabilizing-libtests-json-output/20163). [#50297](https://github.com/rust-lang/rust/issues/50297), on the other hand, seems far off. That's unfortunate, since we could probably do really cool stuff with it, without being too hacky.

`--show-output` together with `--format json` seems especially cool. Any `println!` in the tests turns into ```json { "type": "test", "name": "some_test", "event": "ok", "stdout": "hey\n" } ```

With the "generate an `index.ts`" feature in mind, the CLI needs *some* way to get a list of all TS types and their respective `.ts` files. Solutions I can think...

> I think this might be the best way to go. Use the mutex file lock to append to a metadata file all the types' names anc paths, then parse...

This all kinda makes me curious - How would it look like if we tried to do that without a CLI? Gotta play with that during the weekend!

> My guess is that it'd be pretty much impossible, at least the way we've implemented it so far, as it heavily relies on doing stuff after cargo test has...

I'm at a similar place as @gustavo-shigueo - I'd love to integrate (more) with wasm-bindgen, but my experience with it is very limited. The few times I used it I...

@eye-wave I'd be interested in how you do (de)serialization such that you'd profit from ts-rs generating typed arrays. What format are you using for (de)serialization, and which libraries do you...

I'm really unsure about this. For the use-case I most often have in mind - JSON APIs - this would be super weird, since there's no correlation there. Am I...

I would like to support this, but I'd just like to not that this is not an easy feature to implement *properly*. Exporting multiple types to a single file will...