Support plan

• is this issue currently blocking your project? (yes/no): no
• is this issue affecting a production system? (yes/no): no

Context

• node version: v12.22.12
• module version with issue: v17.8.1
• last module version without issue: v17.7.1 probably
• environment (e.g. node, browser, native): node
• used with (e.g. hapi application, another framework, standalone, ...): https://github.com/jeffbski/wait-on
• any other relevant information: I'm not condoning use of Node 12, which is past its end of life. This broke an old CI job which was using Node 12. Rather, reporting this due to loss of stated Node versions support (and in a minor increment too).

What are you trying to achieve or the steps to reproduce?

I'm not using joi directly, but via wait-on. From what I can see, the release 17.8 bumped some dependencies to versions that don't claim to support Node 12 (https://hapi.dev/resources/status/).

Having investigated the cause chain myself, I wanted to report this to you rather than let the maintainer of wait-on do it themselves, to avoid repeated work and possibly save other consumers from trouble.

What was the result you got?

Error jeffbski/wait-on#136 , which I believe may have been caused by bumping of joi's dependencies in the 17.8 release.

What result did you expect?

The package is compatible with Node 12, as stated on https://joi.dev/resources/status/#joi