[bug]: React Native: Unable to resolve module http from node_modules/@algolia/requester-node-http/src/createHttpRequester.ts:

[giantslogik]

Description

With
"algoliasearch": "^5.4.3",
"react-instantsearch-core": "^7.13.1",
"react-native": "0.73.6"

the algolia client fails with:

Unable to resolve module http from src/mobile-app/node_modules/@algolia/requester-node-http/src/createHttpRequester.ts: http could not be found within the project or in these directories:
  node_modules
  ../../node_modules
> 1 | import http from 'http';
    |                   ^
  2 | import https from 'https';
  3 | import { URL } from 'url';
  4 |

This worked previously with "algoliasearch": "^4.23.3" and "react-instantsearch-hooks": "^6.33.0"

It appears that the algoliasearch 5 , package is no longer compatible with react native.

This is the same error as #1547 which is incorrectly closed.

Client

Search

Version

5.4.3

Relevant log output

Unable to resolve module http from src/mobile-app/node_modules/@algolia/requester-node-http/src/createHttpRequester.ts: http could not be found within the project or in these directories:
  node_modules
  ../../node_modules
> 1 | import http from 'http';
    |                   ^
  2 | import https from 'https';
  3 | import { URL } from 'url';
  4 |

[shortcuts]

Hey, the client should still be compatible but it leverages package.json#exports field, which is an opt-in metro option

Does it make it work if you enable it?

[giantslogik]

Does not work. It crashes elsewhere which isn't surprising, given that is an unstable and experimental feature.
Does "algoliasearch": "^4.23.3" have better react-native support ? Is this on the roadmap for 5.x ?

[Haroenv]

@shortcuts, you can probably add a react-native (same as browser probably, XHR works in RN) entry point as for some reason the browser entry point isn't taken any more.

as a workaround for now you can of course use v4 still @giantslogik or add an alias to the browser entry point

[giantslogik]

@Haroenv can you elaborate on add an alias to the browser entry point.

I'm migrating away from v4 as it subtly broke my React Native environment by introducing dom types into the react native typescript environment.

[shortcuts]

Does "algoliasearch": "^4.23.3" have better react-native support ?

Yes, it uses the old package.json entrypoints so it should work by default with rn

Is this on the roadmap for 5.x ?

Definitely, mostly @Haroenv suggested, but I was wondering it this could just stay on the bundler side rather than the library side

you can probably add a react-native (same as browser probably, XHR works in RN) entry point as for some reason the browser entry point isn't taken any more.

yup it seems like a requirement, I'll try to see on the expo side as well if there's a consensus before

[giantslogik]

@shortcuts It can't stay on the bundler side, as any bundler options would need to be compatible with every commonly used react native library out there. And it shouldn't need an experimental /unstable feature .

There are other issues with React native support that i will ticket as well. (that have existed from 4.x atleast )

[InefableKoumba]

I am experiencing the same bug.

[InefableKoumba]

Downgrading to "algoliasearch": "^5.2.3" has resolved the issue.

[shortcuts]

hey @InefableKoumba thanks for reporting :)

as per their doc, the browser field at the root is looked up when resolving modules, so algolia/api-clients-automation#3767 should provide a fix for this!

[shortcuts]

Hey, 5.5.0 should have this fixed :)

[FXStreetDeveloper]

Hey there! 5.5.0 version does not fix the bug for me

[Haroenv]

@FXStreetDeveloper, do you still get the same error message? maybe a repo that can be reproduced?