Clarify how this extension works

[juliancoleman]

So, my current process looks like this: I have just installed this extension, I open the commands with ctrl+shift+P, and I begin typing run by typing. From there, it adds runByTyping.js to the root of my project, and also opens up a new pane to the right of my currently opened file, with a console log hello world, and ***runByTypingDone***.

Looks to be promising so far! However, after editing files that have console.log (unfortunately) littered everywhere, I cannot see the output in runByTypingDone. How should I go about being able to run my entire codebase all at once, and seeing my console logs? I am not building an API, so I'm not worried about the debugger tools. I almost just want to run my code in a repl. I'm only building a functional library.

Thanks a bunch in advance!

[juliancoleman]

It looks like I can require my index.js to see the output, but without stack traces.

[pierogitus]

@juliancoleman yes runByTyping.js is essentially like an entry point of a separate program. So you just require whatever file you want to test.

Can you give an example of what you're not seeing with stack traces? I believe they work correctly like with the code below

    try{
        //Some error
    }
    catch(e){
        console.log(e.stack)
    }