Inject custom assertions to types.js by publishing assert in types.js

I would like to add custom assertion so it can be used similarly to test.equal (e.g. test.contains).

The issue is that assert is required in two places:
In nodeunit.js, and in types.js.

The assert in nodeunit is exported, the one in type is not.
If this could be exposed then it would be very easy to add a custom assert and let the mechanism add them to test with the necessary wrapAssert.
Without it, it's still possible to use custom assert but cannot add them to the test level.

Thanks.

Ronnen

Comienza comparando cómo se requiere y exporta assert en nodeunit.js con su uso en types.js. Expón la aserción de types.js para que las aserciones personalizadas puedan envolverse en el objeto test; después ejecuta la suite de pruebas existente y verifica que haya una aserción personalizada disponible en el nivel de test.

Escrito por el modelo de indexación a partir del texto del issue.