Jack Works

@alexcorvi thanks for your work! But I'm afraid it's still incorrect: ```js import anchorme from 'anchorme' console.log(anchorme) // This expression is not callable. console.log(anchorme.list) // TypeScript error, but works with...

see https://github.com/tc39/proposal-defer-import-eval/pull/43

I think we may add some utils in the future so the user don't need to write those host hooks again and again.

> LessThan is M if M < N, otherwise never > GreaterThan is M if M > N, otherwise never Shouldn't LessThan return a boolean literal type instead of number/never?

The TypeScript error is telling you the type of this file cannot be properly named (used a type inside a transitive dependency), thus it is not portable, but since this...

is this a user-aware syntax change or is it just make things technically correct?

I have another question, if you search "scx" in https://unicode.org/Public/UCD/latest/ucd/PropertyValueAliases.txt, you will find there is no record for it. And according to the [spec](https://tc39.es/ecma262/#sec-patterns-static-semantics-early-errors), > [UnicodePropertyValueExpression](https://tc39.es/ecma262/#prod-UnicodePropertyValueExpression) :: [UnicodePropertyName](https://tc39.es/ecma262/#prod-UnicodePropertyName) = [UnicodePropertyValue](https://tc39.es/ecma262/#prod-UnicodePropertyValue)...

> Hi, thanks for the contribution! > > In Lingui v5, this may be less relevant due to the new [`useLingui`](https://js-lingui-git-next-crowdin.vercel.app/releases/migration-5#introducing-uselingui-macro) macro which allows to use the `t` macro inside...

Hi! Thanks for the review, before resolving any issue, I wonder if we still need this lint in v5? If not, I prefer to close this PR (or we can...

> I checked the code: > This fix requires type-aware lint and only applies when the context accepts a React.ReactNode. > It looks very complicated The type-aware fix is optional,...