As part of our continuous effort to focus and deliver the best search & discovery developer experience, Algolia has made the decision to deprecate the Angular InstantSearch package.
Below are frequently asked questions to help you understand the reasons behind this decision, its impact on your projects, and how you can transition smoothly to alternative solutions.
1. Why is Angular InstantSearch being deprecated?
The decision to deprecate Angular InstantSearch stems from the challenges posed by the transition to Angular’s Ivy engine, and the elimination of the compatibility compiler. More information here.
2. What should I do if I’m currently using Angular InstantSearch?
We recommend upgrading to a modern version of Angular and migrating to InstantSearch.js. We have provided a detailed guide to help you with this migration.
3. Will you still support Angular InstantSearch after deprecation?
The package will no longer be fully supported. Deprecation means we will not be actively maintaining or supporting Angular InstantSearch. However, it will still be available for use for a limited time. The package will be marked as deprecated on npm in 3 months (2024-09-05). After this date, the package will no longer be actively maintained, and the documentation will be archived.
Version | Status | Announcement | End of Support |
v4.x | Deprecated | 2024-06-06 | 2024-09-05 |
As the library will no longer receive updates, any new vulnerabilities discovered will not be patched. This poses potential security risks for projects that continue to use it, as with any out-of-date package. While customers can choose to fork the code and maintain it themselves, this approach may require significant effort and expertise to ensure continued security and stability.
5. Where can I find the migration guide?
The migration guide is available here.
6. How can I get help during the migration process?
Please reach out through our support channels if you need assistance.