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
I’m developing an Expo/React Native app and hit two compatibility issues with near-api-js due to Node.js-specific imports, which React Native doesn’t support. These suggest a broader need for official React Native compatibility.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I’m developing an Expo/React Native app and hit two compatibility issues with
near-api-js
due to Node.js-specific imports, which React Native doesn’t support. These suggest a broader need for official React Native compatibility.Issue 1: @near-js/providers and
http
node_modules/@near-js/providers/lib/fetch.js
http
, failing in React Native.fetch
.Issue 2: @near-js/accounts and
crypto
node_modules/@near-js/accounts/lib/local-view-execution/runtime.js
crypto
, failing in React Native.expo-crypto
forgetRandomValues
andsubtle.digest
.Mobile apps are key for blockchain adoption, and React Native is a popular choice. Native support would make NEAR more accessible to mobile devs.
Happy to help test or contribute if needed!
Beta Was this translation helpful? Give feedback.
All reactions