Artem Govorov

@vjau Thanks for your note, we have added the node version restriction to the docs: https://wallabyjs.com/docs/integration/vitest.html#article.

When Wallaby starts, it uses a library to scan for files and tests patterns. Looks like in your case the library exits (possibly by timeout) before the file system scan...

@IPWright83 Please check this [docs section](https://wallabyjs.com/docs/intro/install.html?editor=sublime#sublime-text): > you may use node_path setting in your User/Wallaby.sublime-settings file to specify the full path to node.js executable file. ``` { "node_path": "your/nodejs/path/node" }...

@IPWright83 Thanks for your feedback. We have a close plan to re-work our docs, and we'll address the discoverability concern for this type of issues as a part of it.

Could you please create a sample repo with some failing tests so I could have a look? All tests in this repository are running ok with wallaby. Maybe also try...

> Wallaby seems to be transforming the same typescript file more than once Can you please share a bit more details about what led you to this conclusion? Are there...

Thanks for reporting the issue. From the logs it looks like you are using `ts-jest`, and we have seen some `ts-jest-transformer` caching specific issues in past, that were not caused...

Awesome, thanks for the update! If you would like us to investigate why Wallaby was misbehaving in the setup with a nested git submodule that also has jest related config,...

Hello, thank you! The limit is 4096 chars per message, 19290 is the total length of the string being logged in this case. The limit helps to run tests faster,...

Sure, marking it as a feature request.