Sven Sauleau

@jschwartzentruber prism 1.16.0 has been fixed: ``` $ curl https://cdnjs.cloudflare.com/ajax/libs/prism/1.16.0/prism.min.js -vvv | sri-sha512 b6x3q+bsDBUcTzuCP9rsvFzqb/LJgkSxy7J0K3M+BFubzcLFkJTOoLG/GYfZr4W65qFV25PIxn+KmlQnoZPAWw== $ curl https://cdnjs.cloudflare.com/ajax/libs/prism/1.16.0/themes/prism.min.css | sri-sha512 zpEXay1ygEa8Bjw1KCXJwsP2BvHNwiB9kYH+fnZmesHI6ixnaN49rcR8X9gx7SfzOW1lybh/TKvcqldC+SLc2w== ```

codemirror 5.48.4 has been updated. @wh1t3t1p would you be able to double check?

Closing this issue as all the affected libraries have now been restored.

What do you think about https://github.com/stalwartlabs/sieve/pull/7? This makes it possible for projects to consume the Sieve parser.

@syrusakbary I will give it a try. I believe I can use the [Backtrace](https://docs.rs/backtrace/0.3.67/backtrace/struct.Backtrace.html) information when a [RuntimeError](https://docs.rs/wasmer/latest/wasmer/struct.RuntimeError.html) and/or [Trap](https://docs.rs/wasmer-vm/3.1.1/wasmer_vm/enum.Trap.html) occurs. This should give us a initial / basic coredump...

@syrusakbary I opened https://github.com/wasmerio/wasmer/pull/3626 for adding basic coredump generation using the existing APIs. It's inpired by the change I did for wasmtime and wrote some documentation: https://github.com/bytecodealliance/wasmtime/blob/db931d7a93208738b8106e8d8c1a4afc8efaca6d/docs/examples-coredump.md.

Basic coredump generation has been merged (thanks!). Now, to have the complete debugger experience, we need to collect the following information: - Wasm locals of each stack frames; when discussing...

The merged PR only has a limited support to Wasmer, most of the features aren't implemented because we are missing access to locals and main memory.

@syrusakbary I'm not familiar enough to do it myself

Btw please feel free to PR the documentation to clarify this here: https://github.com/ByteArena/docs