Port several types from tap-yaml

[isaacs]

Happy to split this up into multiple PRs if it's easier to review separately, or send a smaller PR if only some are desired.

This is about 80% of the way to being able to just drop tap-yaml entirely in favor of yaml-types, which would be nice.

[eemeli]

Very promising! Happy to consider all of these at once. Did a first pass, but ran out of time before getting to !function and !nullobject. See comments inline.

[isaacs]

Resolved the typos and style stuff etc that you caught, thanks for the review.

[eemeli]

Finally got around to this again; sorry for the delays. Two inline comments still to resolve; I think Domains ought to get left out for now. Happy to reconsider later if another use case for them comes up.

[isaacs]

Pulled out !domain, and updated !error with the patch I suggested, if that works. (I'm not opinionated about it, if you wanna land it the way you suggested, that works fine too.)

And actually, now that I think about it, since domains are deprecated and not really used much anymore, tap probably shouldn't give them any special treatment, and instead just remove them from the diagnostic objects anyway.

[eemeli]

It looks like there are a few remaining test & lint errors. Other than those, I think this is good to merge.

I sent you an invite to the repo, which should let the CI tests run automatically.

[isaacs]

Sweet, thanks! I'll take a look this afternoon and see if I can't get the CI passing.

[isaacs]

Test failure was because ??= was being used to test against a false value, because typeof === 'function' returns false, not null.

Fixed and ready to land, just waiting for CI to complete.

[isaacs]

@eemeli merged, but you've got the publishing keys ;)

[eemeli]

Done! Ended up releasing yaml 2.3.0 first, and added that as a minimum dependency here.