Algolia Support for Angular InstantSearch
loveraimogen opened this issue · comments
Background
Angular has evolved significantly with the removal of the legacy view engine in favor of Ivy, and the ecosystem is continuously advancing, as seen with the recent release of Angular v17. This has brought up questions about Algolia’s future support of angular-instantsearch.
Update
We are aware of the challenges and the importance of this library to your projects and are currently evaluating the best path forward, considering the complexities involved with updating the library to be fully compatible with the latest Angular version.
We want to ensure that we approach this transition thoughtfully and effectively and we invite you to share your thoughts on the library's importance to your work and any specific challenges you're facing due to the current compatibility issues.
Feedback
If you have suggestions or are willing to contribute to the library's development, we're open to reviewing pull requests.
Please use this issue to share your feedback, ideas, and any contributions you might have. Your input is crucial as we navigate the future of Angular InstantSearch.
Angular has moved on to v17, the issue remains a stumbling block. This is the error given when compiling an Angular v16 or v17 application:
Error: src/app/app.module.ts - error NG6002: 'NgAisModule' does not appear to be an NgModule class.
This likely means that the library (angular-instantsearch) which declares NgAisModule is not compatible
with Angular Ivy. Check if a newer version of the library is available, and update if so.
Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.
Feedback is simple, make sure angular-instantsearch supports latest Angular.
Clear communication on whether or not you plan on updating this library to support angular going forward is key.
Just adding my 2 cents in support of the importance of ensuring that angular-instantsearch works with the latest version of Angular. Angular is a very widely used web development framework and the angular-instantsearch is certainly a good motivation/reason to use Algolia for these web apps. angular-instantsearch is one of the main reasons why we decided to use Algolia. Thanks!
Never going to happen. We are waiting for so long. I decided to give up and implement my own UI components that communicates through my "proxy" Web API that uses Algolia API. It is slightly slower but its not noticeable.
This is such an important issue... Angular latest versions bring big advantages and if we cannot use instantsearch then it is a huge blow to both communities
When I was in the process of using Angular 16, I have problems with the compatibility between Angular 16 and Angular-instantsearch, are there any news about this problem?
We selected Algolia, more precisely the InstantSearch module; however, this choice posed significant challenges for both me and my clients. The problem comes from the inability to update to the latest version. Without a comprehensive plan in place, we find ourselves forced to explore alternative solutions. Despite all the investments made with algolia
Our company is responsible for the development of several high-traffic dynamic websites, all utilizing Algolia and Angular. Unfortunately, we continue to face significantly long page loading times. This is why the migration to Angular versions v16 and v17 has become an urgent necessity that cannot be further delayed. At the same time, it is crucial for us to maintain our use of Algolia. We have been stuck in this situation for several months, and it is creating a risky dynamic with our clients. We urgently request you to update Angular InstantSearch as soon as possible so that we can significantly enhance the development of our websites. Thank you for taking swift action to address this issue.
Are there any updates or progress to share on this issue? Will this ever be implemented or are newer versions of Angular basically excluded from using Algolia (or everything that relies on InstantSearch)?
Are there any updates or progress to share on this issue? Will this ever be implemented or are newer versions of Angular basically excluded from using Algolia (or everything that relies on InstantSearch)?
Yeah it would be good to get some notification of intent here... I have spent the last year building a product based on angular and instantsearch.. I need to migrate to latest versions of angular soon.. if there is no intent to support angular i need to think about moving to another framweork and doing a rebuild :(
Hopefully, the team will update angular-instantsearch to supports with the latest Angular version.
This is a major issue. Please let us know if you plan to support angular.
Definitely want to see InstantSearch supported in the latest Angular. Would be a major setback to our progress using Algolia if we lost InstantSearch
Any further decisions here : I really need this to happen or i need to look at alternatives
Any further decisions here : I really need this to happen or i need to look at alternatives
Clearly this does not seems to be a priority. You should consider switching to another provider. This has pretty much screw us (waiting for months) and made us a realize that Algolia team is not ready to support you here. We started migration to another tool and it isn't that scary as we thought. With Algolia pricing we will actually save money over time anyways...
The lack of communication clearly means it is not being worked on sadly.
Any further decisions here : I really need this to happen or i need to look at alternatives
Clearly this does not seems to be a priority. You should consider switching to another provider. This has pretty much screw us (waiting for months) and made us a realize that Algolia team is not ready to support you here. We started migration to another tool and it isn't that scary as we thought. With Algolia pricing we will actually save money over time anyways...
Any good recommendation?
We are prepared to assist in getting Angular InstantSearch working again with the latest versions of Angular. My colleague @johan-- , a competent and experienced Angular developer, has been going through the instantsearch code extensively and he has made some changes and has submitted a Pull request more than a month ago already, without any response yet from Algolia. In the Pull request he also requires input from Algolia to be able to make further progress. No feedback has yet been received.
@loveraimogen please provide feedback regarding the priority and future of Angular InstantSearch.
I'm working on a big enterprise webshop, which have used this library for a long time. This library have hold us back from upgrading from Angular 15 and up, but when I was reading this comment from NateMay, it was clear for me that the best idea is to ditch this library completely for our own sake and also for future upgrades. algolia/angular-instantsearch#994 (comment)
With few weekly downloads, I don't believe that the Algolia team will ever prioritize this project.
I'm working on a big enterprise webshop, which have used this library for a long time. This library have hold us back from upgrading from Angular 15 and up, but when I was reading this comment from NateMay, it was clear for me that the best idea is to ditch this library completely for our own sake and also for future upgrades. algolia/angular-instantsearch#994 (comment)
With few weekly downloads, I don't believe that the Algolia team will ever prioritize this project.
Im coming to the same conclusion...
I actually use Meilisearch not Algolia. Meilisearch can be self-hosted with no cost. It doesn't have all the features of Algolia but is extremely fast and has core features you will need for a very good search experience.
You can see it in action here : https://www.ultraislife.com/en/uniqs/marketplace
Meilisearch makes use of the instantsearch libraries but I am now spending time building the UI myself and wiring it to the Meillisearch api. It isn't as much work as I maybe thought and this will allow me to remove instantsearch dependencies and upgrade angular
Angular InstantSearch is a key component of our ticketing system. Please support current versions of Angular as soon as possible. We are now two versions behind.
@loveraimogen is their any indication from the team about what is happening with this issue?
The Ivy Engine became the default Angular compiler with the release of Angular v9, released in February 2020. That's more than 4 years ago. It's a bit worrying in a fast paced reality as the FE world is, nothing has been planned since then to migrate to a more modern version which supported Ivy.
@loveraimogen Could you please provide some feedback about this specific issue? It would be nice to understand the status of this issue as soon as possible.
Thanks
It's too bad your website stated (until quite recently) that Angular Instant Search was compatible with the latest versions of Angular. I wouldn't have upgraded our Angular version at that time. Unfortunately your website was misleading, or just an outright lie, and I did the upgrade, then had to replace all of our Algolia widgets with our own components and instantsearch.js API calls. Cost me about 100 hours that I can't get back.
Pretty disappointing that Algolia is not supporting Angular 15+. Our application has utilized Algolia and specifically this package for over 4 years and as we worked to upgrade our Angular app, we come to find that this library is not being actively maintained and cannot use it with Ivy. +1 to make this package compatible with Ivy... but, we will have moved off this package and probably Algolia by then.