Add support for tag name inferral in types

[wooorm]

Closes GH-5.

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)
• If applicable, I’ve added docs and tests

Description of changes

See GH-5.

Notes:

• I’m not 100% about type versions. I never used it before. And I wasn’t able to test it. Does this work?
• I couldn’t get parse(null) to return a normal element, or parse(undefined, 'g') to return a g
• Any other tips are more than welcome!

[ChristianMurphy]

Very cool 🤩
A nice addition 🌟

LGTM

[wooorm]

@ChristianMurphy You think

hast-util-parse-selector/package.json

Line 31 in ae1c563

"typesVersions": {

is going to work? I’m not sure how to assert that it does

[ChristianMurphy]

It looks like it does https://github.com/unifiedjs/unified/blob/0f3b92833fd910c21edef423ad5891af7f11a82e/package.json#L39-L46 uses similar syntax.
For testing, I usually pull the code up in VSCode, view the tests/type tests, and switch the typescript version from the menu to see how it responds.
And if that doesn't cut the mustard, I'd symlink with npm link into another project, and do the same process.

[wooorm]

It looks like it does unifiedjs/unified@0f3b928/package.json#L39-L46 uses similar syntax.

Yeah, that’s what I went for. Plus I searched and found that there was an inverted syntax (<=) too.

---

I’ll see if downgrading TS still runs!

[wooorm]

Blargh. No. Doesn’t seem to work

[wooorm]

nvm, it worked fine!

[wooorm]

Released in 3.1.0!