Use native querySelector types instead of copying them

[fregante]

I'm looking for a way to use querySelector’s own types so that:

• they don't need to be copied to our definitions
• enhanced 4.1 querySelector types would be enabled here as well (via typed-query-selector or natively)

Unfortunately I'm stuck on "Type QuerySelector is not generic":

Note: We can't use Parameters<fn> and such because it doesn't support overloads.

[g-plane]

Playground

[fregante]

With the help of this SO answer, I'm starting to understand why this isn't working (but I'm not any closer to a solution).

In short, ParseSelector<string> is like a "TS type function" that accepts a "parameter" and it resolves into another type. querySelector<string>() instead is an actual JS function that's resolved when it's actually called in JavaScript. The closest way to extract its resulting type is via ReturnType<querySelector>, which ignores the overloads and the generics.

---

I think this feature request is exactly what I need to do, but it hasn't been accepted. Its alternative solution includes cascades of extends/infer, as expected. I don't think that's worth over just including typed-query-selector

---

The next ideal solution would be to set elementReady: typeof querySelector and then add the second parameter. Unfortunately this is likely even less doable.

[fregante]

Maaybe this? microsoft/TypeScript#33185 (comment)

[sindresorhus]

@fregante Can you move this to an issue? In case someone comes along and knows a good way to solve this.