Native node TestContext.assert is not typed correctly about typescript HOT 6 CLOSED

This is working as intended per #32695. Assertions require every name in the call target to be declared with an explicit type annotation.

from typescript.

I've got three questions.

1. Every name in the call target needs to be declared with an explicit type annotation. TypeScript knows the types involved. Why does the parameter need to be explicit? I've read the issue and others like it but I failed to find the underlying reason why explicitly typed parameters are required or a workaround.

2. Why does the native assert package work?

TypeScript Playground

3. Using the native assertions doesn't help with the test plan when one is required. Can @types/node be updated so the first example works? If so, is that a ticket for DefinitelyTyped/DefinitelyTyped?

I appreciate any extra detail or dumbing-down of the information that you can provide.

from typescript.

1. This limitation is by design for performance reasons.
2. This library does not require your passed function to be an assertion function, or there are no identifiers without declared type (didn't check which one).
3. That would be a bad change. I'm sure it's intentional that it requires an assertion function.

from typescript.

This issue has been marked as "Question" and has seen no recent activity. It has been automatically closed for house-keeping purposes.

from typescript.

I don't think this is a TypeScript issue per se, but it is weird that this works when node:assert is imported directly, but it doesn't when it's used off of node:test's TestContext object which, as far as I know, just re-exports node:assert.

from typescript.

I expect this is an issue with @types/node instead and how it's typing TestContext's assert:

Note when it's off of node:assert it's a full function, but it's a lambda when it's on TestContext.

from typescript.