#console-log #console #logger #logging #log #front-end

wasm-logger

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

7 releases

0.2.0 Nov 15, 2019
0.1.5 Jun 16, 2019
0.1.3 Apr 13, 2019
0.1.2 Feb 15, 2019
0.1.0 Oct 4, 2018

#125 in Debugging

Download history 17089/week @ 2023-12-17 8808/week @ 2023-12-24 14745/week @ 2023-12-31 22003/week @ 2024-01-07 20034/week @ 2024-01-14 17359/week @ 2024-01-21 20595/week @ 2024-01-28 23345/week @ 2024-02-04 23477/week @ 2024-02-11 12830/week @ 2024-02-18 11145/week @ 2024-02-25 14518/week @ 2024-03-03 16016/week @ 2024-03-10 23068/week @ 2024-03-17 18411/week @ 2024-03-24 17577/week @ 2024-03-31

75,815 downloads per month
Used in 64 crates (46 directly)

MIT/Apache

16KB
135 lines

wasm-logger

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-logger = "0.2.0"

Initialize wasm-logger when your app start:

wasm_logger::init(wasm_logger::Config::default());

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

Log for a specific module only

You can provide a path prefix:

wasm_logger::init(wasm_logger::Config::default().module_prefix("some::module"));

then, wasm-logger 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