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

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

#255 in Debugging

Download history 7291/week @ 2024-12-30 15072/week @ 2025-01-06 14601/week @ 2025-01-13 12128/week @ 2025-01-20 11084/week @ 2025-01-27 17380/week @ 2025-02-03 12557/week @ 2025-02-10 11668/week @ 2025-02-17 12962/week @ 2025-02-24 12679/week @ 2025-03-03 12848/week @ 2025-03-10 13931/week @ 2025-03-17 14629/week @ 2025-03-24 10297/week @ 2025-03-31 13789/week @ 2025-04-07 24081/week @ 2025-04-14

63,764 downloads per month
Used in 82 crates (59 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

~7–10MB
~181K SLoC