#console #log #front-end

wasm-log

A logger that sends a message with its Rust source's line and filename to the browser console

1 unstable release

0.3.1 Nov 25, 2022
0.3.0 Nov 25, 2022

#647 in Debugging

Download history 144/week @ 2023-11-20 163/week @ 2023-11-27 146/week @ 2023-12-04 105/week @ 2023-12-11 55/week @ 2023-12-18 4/week @ 2023-12-25 2/week @ 2024-01-01 66/week @ 2024-01-08 106/week @ 2024-01-15 13/week @ 2024-01-22 81/week @ 2024-01-29 48/week @ 2024-02-05 26/week @ 2024-02-12 45/week @ 2024-02-19 122/week @ 2024-02-26 55/week @ 2024-03-04

248 downloads per month
Used in 4 crates (3 directly)

MIT/Apache

21KB
149 lines

wasm-log

A logger that sends a message with its Rust source's line and filename to the browser console.

screenshot

Usage

Note: For more information about how to use loggers in Rust, see log.

Cargo.toml

[dependencies]
log = "0.4.6"
wasm-log = "0.3"

Initialize wasm-log when your app start:

wasm-log::init(wasm-log::Config::default());

// Logging
log::info!("Some info");
log::error!("Error message");

Log for a specific module only

You can provide a path prefix:

wasm-log::init(wasm-log::Config::default().module_prefix("some::module"));

then, wasm-log only logs message from some::module

Mapping from log to console's methods

log::error!, log::warn! and log::info! call theirs equivalent methods of the browser console. The console.trace method outputs some extra trace from the generated JS glue code which we don't want. Therefore, we choose to map:

  • log::debug! to console.log
  • log::trace! to console.debug.

Note for Chromium/Chrome users

Chromium/Chrome filters out console.debug (execute by log::trace!) by default. You must check the Verbose filter in your browser console to see trace entries.

License

MIT or Apache-2.0

Dependencies

~6.5–9MB
~171K SLoC