Artem Govorov

We have investigated a bit and depending on how exactly you've been editing your code to add the `finalIDs//?` line, it may be possible for the debugger to shift the...

We don't yet have any particular plans to add the support for the bundler, but the good news is that wallaby does support other bundlers, like [webpack](https://github.com/jeffling/wallaby-webpack) and [browserify](https://wallabyjs.com/docs/integration/browserify.html), via...

@nbilyk Your `files` src pattern has a typo (supposed to be `src/**/*.js`). After making the change (also adding test resources used in the tests and [setting to reload workers](https://wallabyjs.com/docs/integration/esm.html#mocha)), this...

None of these options are available at the moment, so I'll mark it as feature request.

> Is it possible to have untested files show 0% coverage rather than N/A? This is how Jest's coverage tool works Are you using configuration file, or Jest auto-config feature?

> Is it possible to have untested files show 0% coverage rather than N/A? This is how Jest's coverage tool works We have implemented the feature in the [the latest...

Not really sure if some good solution exists for this issue. While Wallaby can intercept `console.log(error.stack)` at runtime, the `console.log` argument for Wallaby at this stage is just a string....

> Do you have an idea how to go about it, using the sourcemaps Wallaby generates? Only by maybe exposing some Wallaby specific API that you will need to use...

If your slower tests are located in a separate file(s), then one thing I may suggest before the feature is implemented is to perhaps have 2 wallaby config files. One...

Thanks for the suggestion, will implement tap support in planned node.js runner.