There are so many issues and no fixes. Please, let us know if this plugin hasn't support anymore...
adamasantares
All 5 comments
Apparently this project is no longer maintained as discussed here: https://github.com/twitter/typeahead.js/issues/1424
It was recommended to use https://github.com/corejavascript/typeahead.js but that hasn't been updated for 8 months so I'm not sure if that's the best solution either.
https://github.com/algolia/autocomplete.js was also recommended and it has recent activity.
MrHubble
on 6 Sep 2016
Feature-wise, there are a few better options
Both are a bit heavier than typeahead.js but have a lot more features like multiple select, pagination, infinite scroll, mobile support etc.
Select2 is slightly bigger than selectize.js and extending it is complicated in the current version (4.x). Hence I've found selectize.js to be a good replacement for my projects.
bitcity
on 6 Sep 2016
@bitcity thank you for links, but my problem is that the client's project uses this plugin and I can't change it to other plugin for now :(
adamasantares
on 6 Sep 2016
As someone who uses the library in a few projects I would highly welcome a canonical fork (ideally with a notice in this repo) in the hands of someone who has the time and energy to maintain this.
I'd also note to Twitter devs that it is much better for reputation and brand to pro-actively identify unmaintained projects and mark these as such clearly at the top of the README so the community knows it is OK to create a new canonical fork (and offering to include a link to that fork from your repo).
josephearl
on 21 Sep 2016
My choise is https://github.com/pawelczak/EasyAutocomplete
adamasantares
on 23 Sep 2016
Related issues
thedavidscherer
路
5Comments
agborkowski
路
5Comments
GreatPotato
路
8Comments
svlcomyoo
路
4Comments
steswinbank
路
5Comments
Most helpful comment
As someone who uses the library in a few projects I would highly welcome a canonical fork (ideally with a notice in this repo) in the hands of someone who has the time and energy to maintain this.
I'd also note to Twitter devs that it is much better for reputation and brand to pro-actively identify unmaintained projects and mark these as such clearly at the top of the README so the community knows it is OK to create a new canonical fork (and offering to include a link to that fork from your repo).