Simen Bekkhus
Simen Bekkhus
@h2non Any news here? 😄
One not mentioned in the OP is [`cypress`](https://testing-library.com/cypress)
It seems they'll deal with that themselves  But at least `prefer-explicit-assert` would be nice
Yeah, that's what I meant 👍
Why not tell people to use https://github.com/facebook/jest/blob/6fc1860a34ea64a7c3360580e2874c94a5c8fc83/packages/jest-types/src/Config.ts#L43-L51?
`Error.message` is a string according to the node docs: https://nodejs.org/api/errors.html#errors_error_message. How are you creating the error where `message` is not a `string` without breaking that contract?
Where in the docs is it defined as "user readable"? It clearly says `` in node's docs, which is the runtime of this library. (FWIW, I agree we shouldn't break...
I fully support it behind an option 🙂
+1, Levee also has a "half open" concept. https://github.com/krakenjs/levee/blob/master/README.md
Yeah, an action running the update script should be fine. One snag is that we need to wait for the musl builds to complete so we can get them from...