Introducing tracing-web to the ecosystem #2280
Comments
hawkw
pushed a commit
that referenced
this issue
Aug 25, 2022
Fixes #2280 ## Motivation I've implemented an alternative to [`tracing-wasm`] to fix some issues that I had when using it (most are open as longer time bug reports, no need to recount them here). It should be more up to date with the current tracing framework and, being layer based, is easier to compose with other subscribers, e.g. supports formatting and timing on event logs out of the box. ## Solution Add the [`tracing-web`] crate to the list of related crates. [`tracing-wasm`]: (https://github.com/storyai/tracing-wasm) [`tracing-web`]: https://crates.io/crates/tracing-web/
davidbarsky
pushed a commit
that referenced
this issue
Sep 8, 2022
Fixes #2280 ## Motivation I've implemented an alternative to [`tracing-wasm`] to fix some issues that I had when using it (most are open as longer time bug reports, no need to recount them here). It should be more up to date with the current tracing framework and, being layer based, is easier to compose with other subscribers, e.g. supports formatting and timing on event logs out of the box. ## Solution Add the [`tracing-web`] crate to the list of related crates. [`tracing-wasm`]: (https://github.com/storyai/tracing-wasm) [`tracing-web`]: https://crates.io/crates/tracing-web/
hawkw
pushed a commit
that referenced
this issue
Sep 19, 2022
Fixes #2280 ## Motivation I've implemented an alternative to [`tracing-wasm`] to fix some issues that I had when using it (most are open as longer time bug reports, no need to recount them here). It should be more up to date with the current tracing framework and, being layer based, is easier to compose with other subscribers, e.g. supports formatting and timing on event logs out of the box. ## Solution Add the [`tracing-web`] crate to the list of related crates. [`tracing-wasm`]: (https://github.com/storyai/tracing-wasm) [`tracing-web`]: https://crates.io/crates/tracing-web/
hawkw
pushed a commit
that referenced
this issue
Sep 19, 2022
Fixes #2280 ## Motivation I've implemented an alternative to [`tracing-wasm`] to fix some issues that I had when using it (most are open as longer time bug reports, no need to recount them here). It should be more up to date with the current tracing framework and, being layer based, is easier to compose with other subscribers, e.g. supports formatting and timing on event logs out of the box. ## Solution Add the [`tracing-web`] crate to the list of related crates. [`tracing-wasm`]: (https://github.com/storyai/tracing-wasm) [`tracing-web`]: https://crates.io/crates/tracing-web/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The tracing-wasm crate - which is currently linked in the Related Crates section - seems to have several open issue that might take a lot of effort and re-engineering to fix. Most prominently, it doesn't offer a configurable layer based subscriber (the layer handles formatting, events and spans all in one).
I've written tracing-web to fix several of these issues and implemented a
tracing-subscriberbased, web browser/wasm compatible tracing subscriber. Could you please add this to the list?If you have a lot of time, you are also invited to try it out and give me a bit of feedback :)
If you want me to write the PR to add myself to the list, I can do that too.
The text was updated successfully, but these errors were encountered: