`typeahead` is not namespaced

[TomHAnderson]

This library is very useful for widget development where HTML is being injected into an unknown website, but the lack of namespacing of the core function threatens collisions. This library defines one global function called typeahead. I'm very concerned that should I use this library it will collide with my client's website. I'm injecting HTML directly into their pages as widgets.

So, although I do not have an example of such a collision I'm very wary about it. This is my suggested solution:

export default function digitalfortress$typeahead<T extends Dictionary>(config: typeaheadConfig<T>): typeaheadResult {

I understand such a central change to this library would necessitate a major version number and would cause a bit of documentation rewriting, but other than that I don't foresee much of a problem.

[TomHAnderson]

Other libraries have addressed namespacing differently but this library defines a global function so this approach may not be as appropriate

https://www.algolia.com/doc/ui-libraries/autocomplete/api-reference/autocomplete-js/autocomplete/

<script src="https://cdn.jsdelivr.net/npm/@algolia/autocomplete-js"></script>
<script>
  const { autocomplete } = window['@algolia/autocomplete-js'];
</script>

[niketpathak]

Hello,
Thank you for your suggestion. Although the chance for collisions remains pretty slim (given that these days, its pretty common to bundle an app into a single javascript file thereby not exposing typeahead to the window object at all). Nonetheless, for people who intend to directly use the library (for example via CDN) could face collisions, so this will be taken into consideration for the next major release. Thanks again.