Mario Gutierrez

Yes, those are all simulated errors from the demo. The error stack is raw. You have to use pretty if you want the runtime entries to be removed.

I'm closing this. Please create a new issue on logxi if there are more issues.

You're right. I'll look into this before I release v2.

I'm going with the simplest method and just using v1, v2 directories. The problem with gopkg.in is it doesn't work with subpackages unless I rewrite all my import paths. With...

use `godo server --verbose` to print files I'll look at the Debounce logic

will be fixed as part of #24 and v2 refactor

I found a workaround for a different stting that had the same error. I added `jestrunner.jestPath` setting to my `.code-workspace` file. For example ```json { "folders": [ { "name": "root",...

I'm in the Philiippines where internet can be spotty. If I restart the computer with no internet connection I see the nag message. Here's an idea. Create an encrypted token...

@JIM-CHEN I have same issue. Nothing locally. Most of our actions are async so this package is not very useful at the moment.

Something like this? `store.js` ```js // i'm using ink so this is regular node not ES6 imports const React = require("react"); const Bank = require("./Bank"); const Counter = require("./Counter"); const...