Artem Govorov

> Jest is on watch and still it does not detect the issues in the code for failed cases. Console Ninja is not handling errors from testing frameworks, only console.logs....

Just noticed that you are not running Jest directly, but are using `@salesforce/sfdx-lwc-jest`. We have a working Jest tests sample, but maybe `@salesforce/sfdx-lwc-jest` works somehow differently or wraps Jest in...

We have ran a few tests Jest is working as expected (prints logs), however `@salesforce/sfdx-lwc-jest` on the same test does not, likely because `sfdx-lwc-jest` spawns/kills Jest process before Console Ninja...

> Can you please send me the recording of the Jest working with Console ninja pls? Sure: 

Right now, if the very root of the monorepo is opened in VS Code as project (and not an individual package), then running dev server in individual packages should work....

> Does it matter run dev server from root or subfolder? After the next release (v0.0.29+) it should not matter and if the root of the repo is opened in...

Console Ninja now ships with built-in **Turbopack** support. Fire up a modern Next.js project (where `npm run dev` runs Turbopack by default) and Console Ninja will now seamlessly capture and...

Hi, thanks for reporting the issue. We have released a new version 1.0.442 that should fix the problem. Can you please update to the latest version when it becomes available...

@bpasero @jrieken Thanks for bringing this up. We are indeed using code lens in output channels, very extensively in [Quokka](https://marketplace.visualstudio.com/items?itemName=WallabyJs.quokka-vscode&ssr=false#overview) Code lens are a great fit for our use case...

@jrieken Awesome, thanks a lot!