Ruslan @doasync

I fixed my issue by removing the **caret** in `"react": "^16.7.0-alpha.2"` Here is the full comment: https://github.com/facebook/react/issues/14454#issuecomment-449585005

> why 'every' use case is better to be default than 'some' Maybe because the array in the filter is intuitively implied as a set of preconditions, and a precondition...

Company: **Stellar Development Foundation** Industry: *Blockchain Network, Cryptocurrency, Finance, FinTech* --- Project: **StellarX** (https://www.stellarx.com/) StellarX is the first full-featured trading app for Stellar’s universal marketplace.  [SVG logo](https://gist.githubusercontent.com/doasync/41f65d1b4fd5743da12baa77b5235419/raw/5d3579ef27ec31da95a76fba92e62bf32e41465a/stellarx.svg)

UNICEF (United Nations Children’s Fund) [[SVG logo]](https://gist.githubusercontent.com/doasync/67de9046153996117ddd8fe8cc17edd6/raw/573b107d00a7950895eb6f09b633f5c7e046c0d7/UNICEF_Logo.svg)  Project Connect ([projectconnect.unicef.org](https://projectconnect.unicef.org/)) > A live map of all schools in the world and the status of their Internet connection. Open...

@stiff, > So `undefined` would be much better fit for it, especially since nullish coalescing is already part of language. You return an array _index_, and arrays **must use integers**...

Related with #102 and #103

@gaearon, is this issue going to be solved before hooks release?

I have used `resolutions` workaround https://github.com/jaredpalmer/tsdx/issues/926#issuecomment-751936109 with updated versions and it worked too: ```json "resolutions": { "**/@typescript-eslint/eslint-plugin": "^5.4.0", "**/@typescript-eslint/parser": "^5.4.0", "**/jest": "^27.3.1", "**/ts-jest": "^27.0.7", "**/typescript": "^4.4.4" } ```