You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and I still get "Unable to resolve module http" for https-browserify, "Unable to resolve module stream" for cipher-base, and "Unable to resolve module net" for https-proxy-agent, respectively. I'm guessing these 3 packages are not in the list of packages "known to make react native choke"?
They work after manually adding "react-native": { "http": "@tradle/react-native-http" }, "react-native": { "stream": "stream-browserify" }, and "react-native": { "net": "react-native-tcp-socket" } to their respective package.json's
Well, actually, these are the most common modules where this happens. There are also other modules where it happens sometimes, like react-native-http and winston, it's a little different every time I delete node_modules and re-run yarn and ./postinstall.sh. I'm not sure what to attribute this randomness to.
The text was updated successfully, but these errors were encountered:
I'm running
yarn rn-nodeify --install 'crypto,os,buffer,react-native-randombytes,vm,stream,http,https,url,net,fs,zlib' --hack --yarn
and I still get "Unable to resolve module http" for https-browserify, "Unable to resolve module stream" for cipher-base, and "Unable to resolve module net" for https-proxy-agent, respectively. I'm guessing these 3 packages are not in the list of packages "known to make react native choke"?
They work after manually adding
"react-native": { "http": "@tradle/react-native-http" }
,"react-native": { "stream": "stream-browserify" }
, and"react-native": { "net": "react-native-tcp-socket" }
to their respective package.json'sWell, actually, these are the most common modules where this happens. There are also other modules where it happens sometimes, like
react-native-http
andwinston
, it's a little different every time I delete node_modules and re-run yarn and ./postinstall.sh. I'm not sure what to attribute this randomness to.The text was updated successfully, but these errors were encountered: