Repository navigation
The package at "node_modules/parse/node_modules/ws/lib/stream.js" attempted to import the Node standard library module "stream" #2633
Description
Activity
parse-github-assistant commented
on Jun 2, 2025 More actions🚀 Thanks for opening this issue!
ℹ️ You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
found a probable workaround from the expo team
https://docs.expo.dev/versions/latest/config/metro/#packagejsonexports
const { getDefaultConfig } = require('expo/metro-config'); /** @type {import('expo/metro-config').MetroConfig} */ const config = getDefaultConfig(__dirname); config.resolver.unstable_enablePackageExports = false; module.exports = config;i will test to see if this has an impact on Parse, but it seems to take away the error. This issue might be related to ws required by Parse
Reacted by Santiago Gutierrez Barrenechenot related but this error should be in the documentation for latest react-native
https://github.com/uuidjs/uuid?tab=readme-ov-file#getrandomvalues-not-supported
node_modules/parse/node_modules/ws/lib/stream.js: stream could not be found within the project or in these directories:
node_modules/parse/node_modules
node_modules
../../../../node_modules
1 | 'use strict';
2 |3 | const { Duplex } = require('stream');
| ^
4 |"@d11/react-native-fast-image": "^8.9.2",
"@parse/react-native": "^0.0.1-alpha.18",
"@react-native-async-storage/async-storage": "^2.2.0",
"@react-native/new-app-screen": "0.80.0",
"@react-navigation/bottom-tabs": "^7.3.17",
"@react-navigation/native": "^7.1.13",
"@react-navigation/stack": "^7.3.6",
"lottie-react-native": "^7.2.3",
"nativewind": "^4.1.23",
"parse": "^5.3.0",
"react": "19.1.0",
"react-native": "0.80.0",
"react-native-gesture-handler": "^2.26.0",
"tailwindcss": "^3.4.17"- addedtype:bugImpaired feature or lacking behavior that is likely assumedImpaired feature or lacking behavior that is likely assumed
on Jul 5, 2025 same error, latest parse does not work with react 0.79
+1
facing similar issue
found a probable workaround from the expo team
https://docs.expo.dev/versions/latest/config/metro/#packagejsonexports
const { getDefaultConfig } = require('expo/metro-config'); /** @type {import('expo/metro-config').MetroConfig} */ const config = getDefaultConfig(__dirname); config.resolver.unstable_enablePackageExports = false; module.exports = config;i will test to see if this has an impact on Parse, but it seems to take away the error. This issue might be related to ws required by Parse
This is working
Reacted by maxvo1kReacted by Santiago Gutierrez Barreneche and maxvo1kFor Parse SDK < 6.x:
Thisconfig.resolver.unstable_enablePackageExports = false;workaround works.For 7.x:
The following fixes the issue:npx expo install expo-crypto npm install react-native-get-random-values
And add this at the very top of your entry file (e.g. app/_layout.tsx):
import 'react-native-get-random-values';
For 8.x:
None of the above workarounds are effective. The SDK now directly uses Node’scrypto.randomUUID()in lib/react-native/uuid.js, which is incompatible with Expo’s runtime (see error in #2856). A proper React Native–compatible UUID fallback is needed.🎉 This change has been released in version 8.0.4-alpha.1
- addedstate:released-alphaReleased as alpha versionReleased as alpha version
on Jan 27, 2026 🎉 This change has been released in version 8.1.0
- addedstate:releasedReleased as stable versionReleased as stable version
on Feb 5, 2026 what is the fix? i still get the error 8.1.0
@lawrenehi Can you open a new issue?
Apologies, yes this is another issue..
@lawrenehi My bad, I didn't see you were the OP. Can you post the contents of your
node_modules/parse/lib/react-native/WebSocketController.js? Are you seeing any new errors?thanks, it failed on me, but on a second check it was a different issue
crypto could not be founderror. so i cant really check if it is fixed on this version because of the crypto issue which is being fixed here #2858at this time this release is unusable for react-native users
New Issue Checklist
Issue Description
On react-native with expo - build , the launch/build fails with the following error
if you add events and stream, you get http and https error too
Steps to reproduce
Create a react native app using
Actual Outcome
App should build
Expected Outcome
Environment
"expo-system-ui": "~5.0.7",
"expo-web-browser": "~14.1.6",
"parse": "^6.1.1",
"react": "19.0.0",
"react-dom": "19.0.0",
"react-native": "0.79.2",
Server
NA
Database
NA
Client
6.1.1Logs
Android Bundling failed 612ms node_modules/expo-router/entry.js (1315 modules)
The package at "node_modules/parse/node_modules/ws/lib/stream.js" attempted to import the Node standard library module "stream".
It failed because the native React runtime does not include the Node standard library.