Artem Govorov

> The component where I encountered the issue is very large, could this be a cause? We have tried `nx` specifically, also larger components, but still can't reproduce the issue....

The log is displayed when Console Ninja runtime is trying to re-connect to the extension and fails to do so (because Console Ninja extension is stopped or paused). Unfortunately we...

@GreyWuLB It's possible to just pause the extension (with `Console Ninja: Pause` command) without uninstalling. This should help: after pausing/uninstalling restart Vite CLI (ie. stop and start `npm run dev`),...

> I use it in a CRA project, Ah, ok, I thought you are using Vite (as the title of this issue indicates). In your case try running `rm -rf...

@dev-seahouse Yes, WSL should be supported. Please create a separate issue with the details requested in the issue template. Also check out this issue/comment: https://github.com/wallabyjs/console-ninja/issues/53#issuecomment-1358265709 to see if it helps.

@productdevbook You may use `Console-ninja: Allowed Hosts` setting to add more host names/ip addresses.

@fev4 There's no need to uninstall, pausing Console Ninja for the project should suffice. Regarding the error, it's coming from some cache that your tools have created (when Console Ninja...

@fev4 > How does that even happen? Why is this injecting itself into production or dev bundles? The behaviour is fully described in the tools docs at https://github.com/wallabyjs/console-ninja#how-does-it-work (the same...

@AsadNextOlive Please try the steps described at https://github.com/wallabyjs/console-ninja/issues/9#issuecomment-1343698142.

[Support for Bun Vite](https://twitter.com/wallabyjs/status/1702561168655794619) has been shipped in v0.0.222+.