Clément Vannicatte

> Thanks @shortcuts but that doesn't seem to work for me. Ah yes sorry I forgot there's only the multi-index search on the lite client > I did manage to...

> I also just found out after some digging that the lite client doesnt have the "searchSingleIndex" method. Is there a reason for it? Bundle size/keeping the lite client as...

> I just finished migrating our own codebase from Algolia v4 to v5 and found the process _very_ confusing. There's [one page](https://www.algolia.com/doc/libraries/javascript/v5/upgrade/) that I found with "upgrade" examples and it...

> The main problem IMHO is that the (new?) TypeScript types are _extremely_ convoluted and hard to follow. For example, when I Command+Click to see what the definition of `searchSingleIndex`...

Hey @MattIPv4 thanks for trying out the new major :) I resolved the issue because the typing problem should be solved, but the but the documentation problem still remains indeed....

should we wait for someone from your team to review as well, or is it good to go?

Hey, thanks for opening the issue :) The type issue seems to be related to the fact that your backend build resolves to our browser build, rather than the node...

I think you need to hint webpack directly, with something like https://webpack.js.org/configuration/resolve/#resolveexportsfields I don't get why nest resolves to the browser build, we default everything to `node` unless unspecified. I...

Hey @bennettl could you let me know if this error still exist in 5.9.1? I believe the recent changes of the published typescript files might've fixed it. Good point @RLMarkStrudwick...

hey @sand4rt thanks for keeping up with the plugin and finding this new issue :) that's super weird I use this daily and never encountered it, will try to reproduce...