console_error_panic_hook

A panic hook for wasm32-unknown-unknown that logs panics to console.error

7 releases

0.1.6 Feb 15, 2019
0.1.5 Sep 6, 2018
0.1.4 Aug 14, 2018
0.1.3 Jul 19, 2018
0.1.1 May 23, 2018

#17 in WebAssembly

Download history 666/week @ 2018-12-20 1044/week @ 2018-12-27 1036/week @ 2019-01-03 1481/week @ 2019-01-10 1142/week @ 2019-01-17 1291/week @ 2019-01-24 1194/week @ 2019-01-31 1242/week @ 2019-02-07 1298/week @ 2019-02-14 2100/week @ 2019-02-21 1392/week @ 2019-02-28 1223/week @ 2019-03-07 1573/week @ 2019-03-14 1365/week @ 2019-03-21 1668/week @ 2019-03-28

5,915 downloads per month
Used in 37 crates (15 directly)

Apache-2.0/MIT

502KB

console_error_panic_hook

Build Status

This crate lets you debug panics on wasm32-unknown-unknown by providing a panic hook that forwards panic messages to console.error.

When an error is reported with console.error, browser devtools and node.js will typically capture a stack trace and display it with the logged error message.

Without console_error_panic_hook you just get something like RuntimeError: Unreachable executed

Browser: Console without panic hook

Node: Node console without panic hook

With this panic hook installed you will see the panic message

Browser: Console with panic hook set up

Node: Node console with panic hook set up

Usage

There are two ways to install this panic hook.

First, you can set the hook yourself by calling std::panic::set_hook in some initialization function:

extern crate console_error_panic_hook;
use std::panic;

fn my_init_function() {
    panic::set_hook(Box::new(console_error_panic_hook::hook));

    // ...
}

Alternatively, use set_once on some common code path to ensure that set_hook is called, but only the one time. Under the hood, this uses std::sync::Once.

extern crate console_error_panic_hook;

struct MyBigThing;

impl MyBigThing {
    pub fn new() -> MyBigThing {
        console_error_panic_hook::set_once();

        MyBigThing
    }
}

Dependencies

~1.5MB
~27K SLoC