Artem Govorov

> As I understand correctly, to test my code in browser, I need some bundler/runtime script loader ? Right ? You'll need [Wallaby postprocessor](https://wallabyjs.com/docs/config/postprocessor.html) that will call Parcel to build...

Have a look into Webpack integration at https://github.com/jeffling/wallaby-webpack/blob/master/index.js, the file has a comment describing what's going on. Basically the idea is to call Parcel API to (incrementally) compile code and...

I like the idea of providing such a flag. Also, even though it's not a one flag solution, but before the feature is implemented, you may write any files back...

This is not something that can be configured at the moment. The last time we tried to experiment with adding such feature under a setting, it caused performance issues in...

@mprokopowicz Could you please provide some more details about your example? Wallaby supports those expressions and notifies if a part wasn't hit:  If you mean the case when both...

@Boolos No, there're no plans for implementing the support in the immediate future.

@vespertilian It is likely that the startup time is directly affected by the number of tests that Wallaby needs to run initially. > Often I am just working in a...

It depends on what is taking the time. If you have `fit` in one of your test files or `//file.only` comment, and restart Wallaby, then it should only be running...

@vespertilian It should be pretty straightforward to make Webpack only compile certain spec files (and make Wallaby only run those spec files). Given your Wallaby config is named `wallaby.js`, you...

@vjpr Maybe [the `Smart Start` feature](https://wallabyjs.com/docs/intro/smart-start.html?editor=jb) is a better solution in your case than setting env variables (in a hacky or a less hacky way)?