#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

#121 in Debugging

Download history 9307/week @ 2023-12-23 14431/week @ 2023-12-30 22004/week @ 2024-01-06 20127/week @ 2024-01-13 17471/week @ 2024-01-20 20658/week @ 2024-01-27 23156/week @ 2024-02-03 23089/week @ 2024-02-10 13800/week @ 2024-02-17 10747/week @ 2024-02-24 14754/week @ 2024-03-02 15871/week @ 2024-03-09 22955/week @ 2024-03-16 18048/week @ 2024-03-23 18171/week @ 2024-03-30 14744/week @ 2024-04-06

77,713 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