🚀 Feature Proposal

From #10123.

When we find a config file, we should also check if there is a jest entry in any sibling package.json and print a warning that it is ignored.

If using --config we should not warn.

Motivation

Helps the user have correct and consistent

I'd admit the current tests might not cover all use cases.
To make the library more stable for the future, adding tests would be great.
That would also clarify what is supported, and what is not supported but works for now.

It's common when writing scripts that install or configure things to need input from the user (at a minimum, something like 'Press Enter to continue'; at a maximum, to be able to prompt the user for input, with an optional default value, and return that value).

Let's use this issue to design how that would look, and I invite suggestions!

I'm submitting a...

[x] Feature request

Current behavior

When an element that you expect to be visible is not, the error message is Expected element to be visible.

Expected behavior

The error message would include the matcher used to try to find the element.

Minimal reproduction of the problem with instructions

For bug reports please provide the STEPS TO REPRODUCE

based on: https://kafka.js.org/docs/configuration and tulios/kafkajs#298
We may not have the correct settings for the JSConsumer and JSProducer. This issue is to ensure we have them up to date after nodefluent/node-sinek#154 has been merged

We should probably start thinking of moving away from logrus in favor of zerolog for our Golang projects going forward. ZL is supposed to be faster, and have more functionality but IMO the big win is not having to worry about the Sirupsen sirupsen import collision that happens.

The performance benefits look to be somewha