t.assert is not a function about node

[climba03003]

I believe it means the functions inside assert is exposed instead of mirroring the whole assert.

[cjihrig]

I can confirm that it was not my plan for the t.assert object to be the assert() function. Whether that is something we want to support or not - I don't have an opinion either way, as long as it is implemented in a way that the t.assert function could be changed in the future programmatically. I would still like to add an API for decoupling t.assert from the assert module (snapshot tests were the proof of concept for that).

[Quramy]

@cjihrig

I can confirm that it was not my plan for the t.assert object to be the assert() function.

Thanks for your answer !

[Quramy]

If you are not intentionally exposing t.assert(), you may close this issue.

[RedYetiDev]

An object containing assertion methods bound to context. The top-level functions from the node:assert module are exposed here for the purpose of creating test plans.

t.assert isn't a function, but an object, try logging it in the console to see what it can do

(As previously stated by @climba03003)