👍🏼 Looks like this doesn't cause any new test failures.

I'm in favor of merging this, but would like to get #704 resolved first. You are welcome to take a look if you'd like.

This appears to conflict with your other PR. I'll merge it when the conflicts are resolved.

Hi sir! I've resolved all the conflicts! I believe it should be good to go now! 💪 😊

I would love to get util factored completely out, but it is stateful in a couple of places that make that tricky.

this might be a step toward that eventuality, or at least it doesn’t seem to make things worse..

LGTM

I think we could also start using nullish operators, but that would necessitate bumping to node 14 and trunk is still on 10.0.0

@markstos can we land this in 3.x or should this be 4.0?

@jdmarshall It's /probably/ not breaking, but as we are making good progress towards 4.0. But since I think 4.0 will be the next release, we can go ahead and merge.

I got a merge conflict when I tried to rebase to see if this was still viable. util is a very very weird class. maybe making it into a Class doesn't change that for better or worse.

Converting back to draft as there are conflicts to resolve again.

I may try to land this after #816
I’m a little surprised this didn’t break unit tests for extendDeep

I'm now thinking this would be a good candidate for 4.2. I'm hoping to remove most of the deprecated forwarding functions in config.js then, which will make this change have less to touch.