Matthieu Sieben

Edit: not relevant, sorry

My current workaround requires me to write schemas in a quite ugly way: ```js const withCustomWrapper = (fn) => { const joi = Joi.extend(withEnvString) // and more return fn(joi, (s)...

Thanks for your answer. My actual use case isn't really related to env variables, this was more of an example on what I was trying to achieve. I did fear...

I'll also look into the describe/compile which I didn't think about, thanks.

Still happening today. In a (very) large project, containing lots of `ts` files, whenever the entire project is re-built, there are so many `rg` processes being spawned that they end-up...

@jasnell done

@jasnell Is there anything else you need ?

Tests are still needed. Let me know if you agree with the approach before I start writing those. Thanks.

The problem with your way is that it is utterly inefficient as it requires a useless function call in production code... Plus, it does not integrate properly with some code...