Luke Schoen

if i run ```bash swanky node install swanky node start ``` it shows better errors including: ``` bin/swanky-node: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by bin/swanky-node) bin/swanky-node: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29'...

currently getting errors like the following when i try updating the "details" table a few times. it's also updating 'main' in localstorage instead of 'details' key ``` Uncaught RuntimeError: memory...

still getting this error ```rust caught TypeError: Failed to execute 'decode' on 'TextDecoder': The encoded data was not valid. at getStringFromWasm0 (kobold_invoice.js:101:30) at imports.wbg.__wbg_createTextNode_2112894c86841cbb (kobold_invoice.js:359:45) at _ZN6kobold8internal9text_node17hf527cb86fc09f751E (kobold_invoice_bg.wasm:0xb1f43) at _ZN76_$LT$$RF$kobold..diff..Ref$LT$str$GT$$u20$as$u20$kobold..value..IntoText$GT$9into_text17hb11f50f01c8b6fabE...

it panics when i try to write to details.csv file in this commit https://github.com/maciejhirsz/kobold/pull/57/commits/6862305cb2b9d93b76b50223c1835077cbf34972 ```bash nicked at 'failed to write to file "details.csv"', examples/invoice/src/main.rs:96:29 Stack: Error at imports.wbg.__wbg_new_abda76e883ba8a5f (http://localhost:8080/kobold_invoice.js:408:21) at...

Fix broken code after updating from Kobold 0.7.0 to 0.8.0. See https://github.com/maciejhirsz/kobold/pull/57/commits/7cfcfcbd0a910d2187f0de470e4a1de90bb2db61 * `onsave_details` method when uncommented doesn't let me compile the code at all and gives below error even...

> Yeah, that's stretching the limits of what `auto_branch` can do atm, the control flow analysis is pretty dumb because I don't want to pull in `syn` and kill compile...

I found links that showed how to step-through wasm-bindgen Rust code in Chrome Canary or Chrome Dev and it seems to work. I just can't seem to step into where...

Note: I was getting the following error in the browser `caught (in promise) TypeError: Illegal invocation` To fix that I had to remove the `data-reference-types` in index.html file. i couldn't...

> So the problem is your logger drops at the end of `main()`. Ideally `kobold::start` should halt further execution and prevent drops, but I have yet to find a clean...

But I still don't know how to: 1) Get breakpoints to trigger if i put them inside these specific blocks `move |e: Event| {` or `spawn_local(async move {`. For example...