Yegor

> If I run it with the watchAll option to false it works > > ``` > npm test -- --coverage --watchAll=false > ``` It doesn't fix issue for me

I noticed that issue exists because some options have unexpected behavior. In my case I placed **{root}/test/jest.config.js** and despite on I pointed --coverage argument issue was fixed for me when...

The same issue. Reproducible repo [here](https://github.com/Yegorich555/web-ui-pack/tree/issue_coverage) - just clone & run `npm i && npm test`  In my case coverage for single file works correct. When files were 5...6...

> Why not use a script like this? > > ``` > jest --coverage && cat ./coverage/lcov.info | coveralls > ``` Because it doesn't work on Windows. Do we have...

Also doesn't work rule `"scss/at-import-partial-extension-whitelist": "never"`  Repo for testing: https://github.com/Yegorich555/webpack-must-have/tree/bug_scss_lint

@Dearenke it works

Hi. Do we have any movements?

Moreover NavLink returns `isActive: false` for child routes

- ```process.cwd()``` in NodeJs... - package.json can point on the workspace folder. It always in the root A lot of packages use similar logic for defining {root} (jest for example)

> I think this can be closed since this landed in TS 4.3 https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#go-to-def-non-js Yep. I've just rechecked. Looks lite it works now