Sergey Gavrilov

I have the opposite problem. Error is __not__ logged to console in dev build. `The above error occurred in the...`, but nothing is above. So if I `console.error` it in...

@vadixidav So in [this example](https://github.com/actix/examples/blob/master/diesel/src/main.rs#L55) I see that database query is wrapped into [`web::block()`](https://actix.rs/actix-web/actix_web/web/fn.block.html), which run queries on a thread pool while not blocking main http server workers pool. But...

Is there any workaround for this? Eg. would be neat to ignore properties with certain names while deep cloning.

@pvorb I'm thinking about optional `ignoreUnclonableObjects` flag (default: false). Here is [the case](https://github.com/artin-phares/microcosm/blob/master/src/boot/client/utils/clone-state-safely.js): I have deep objects tree which consists of 99% clonable objects, except one of deep objects is...

@kripken > By default emcc will generate a .js file that will instantiate the wasm module and pass it the necessary imports automatically for you. I'm using following command to...

Ok. I simply did not have to use `SIDE_MODULE` flag (which is obviously opposite to 'by default'). This works fine ``` emcc counter.c -s WASM=1 -o counter.js ```

i can confirm webpack v5 dev server doesn't notice changes after rebuild by wasm-pack v0.10.2 downgrading wasm-pack to v0.9.1 indeed fixes the issue. using webpack's polling watch option fixes it...

any known workaround for this?

that's right "only pay for what you use" philosophy works great inside c++/rust where we have strong type system. but here in js it just receives `undefined` for `arrayBuffer.length`, because...

I'm trying to use `prop-types` to validate js schema of external service response on server. And surprised it's just generating console warnings. How do I supposed to react to validation...