Hi @flevi29, I haven't gotten time to investigate. Could this be related to the updates we performed on the generated types?

I'm going to investigate it, but I doubt it's us, we're probably just out of date. Unless previous versions worked fine, but even then it's possible. One thing's for sure, the error message is not being very helpful.

Apparently function search doesn't exist anymore.

I'm actually not sure what's the problem here, Algolia types are such a cluster****, I've opened #1378, for now I'm leaving it.

@Strift Okay, I've taken a look at the source code. There really isn't a search and searchForFacetValues anymore. There's only scheduleSearch now, and it doesn't take any arguments. This requires major changes in the code, but I don't really want to work on this that much. Maybe for now we can require an older instantsearch.js, and when you or anyone else from the team has time to investigate and adapt to the newer version of Instantsearch we'll switch to it.

Thanks for the investigation @flevi29. I'll see how I can prioritize this after the v1.13 release of Meilisearch.

@flevi29 this is how i am currently using it (search() and other func are inside .client)

searchClient={{
                    search: searchClient?.client?.search,
                    searchForFacetValues: searchClient?.client?.searchForFacetValues,
                    initIndex: searchClient?.client?.initIndex,
                    addAlgoliaAgent: searchClient?.client?.addAlgoliaAgent,
                    getRecommendations: searchClient?.client?.getRecommendations,
                    ...searchClient
                }}

This is not only issue of the latest instantsearch. I ran into this issue with react-instantsearch 7.13.9 as well after updating to 0.24.0