Aurora Skye

Bumping this as the only thing that fixed code coverage for our codebase, was to use `v8`. We're on the latest `Jest` version with `@testing-library/vue` (we're still using Vue 2)....

Duplicate of #108

+1 just started getting this error :disappointed:

For anyone still frustrated by this, here's one option using `npm`: - [npm `overrides` docs](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides) **Add this to `package.json`** ```json "overrides": { "eslint-plugin-you-dont-need-momentjs": { "eslint": "$eslint" } } ``` **What...

For anyone still frustrated by this, here's one option using `npm`: - [npm `overrides` docs](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides) **Add this to `package.json`** ```json "overrides": { "eslint-plugin-you-dont-need-momentjs": { "eslint": "$eslint" } } ``` **What...

@Suruat this would be great to merge in, if you agree it fixes #5 :pray:

### Whilst waiting for a REAL solution... _Why not combine both_? Simple but repetitive... I appreciate how irritatingly un-DRY it is though :grimacing:. I'm just happy I can click through...

Just in case this helps anyone else who **does** still want to run tests using `--watch` **and** compile the code coverage with `--coverage`... i.e. ``` --watch --coverage ``` I tried...

> I was able to get everything working fine by simply starting jest with watchAll. Then if I want to see the coverage for a single test I just use...

Seems like it's back to not working for me, unsure if a release broke it or something, no idea :woman_shrugging:. I can confirm what others say though `--watch` doesn't work,...