There shouldn't be any need to keep a direct dependency to typed-query-selector and users would benefit from a single global installation of typed-query-selector.
The problem however is twofold:
it's hard/impossible to make this work with generics, changing the final signature
Element.protype.querySelector(s: Selector): Element | null
$$(s: Selector, parent): Element | undefined
expectElement(s: Selector, parent): Element
select-dom also accepts arrays of selectors, which are silently supported by the browser, but the types don't agree.
There shouldn't be any need to keep a direct dependency to
typed-query-selectorand users would benefit from a single global installation oftyped-query-selector.The problem however is twofold:
Element.protype.querySelector(s: Selector): Element | null$$(s: Selector, parent): Element | undefinedexpectElement(s: Selector, parent): Elementselect-domalso accepts arrays of selectors, which are silently supported by the browser, but the types don't agree.Also requested in https://github.com/sindresorhus/element-ready/issues/32