-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Realm package path . is not exported - expo #6238
Comments
@martilopez Can you provide details about your Windows installation (architecture, version, node version, etc.)? |
Im using node version 21.1.0. My pc s x64 and is in version 22H2 of windows.
And this is the error im getting: |
I am getting this issue too while using WSL2 (or locally on windows) |
Did anyone find the solution to this problem? |
I am not sure if #6482 (comment) is relevant here |
Closing as stale. |
I'm working on a react-native project with expo and i've come across this bug.
Whenever installing realm using:
expo init MyAwesomeRealmApp --template @realm/expo-template
I get the following error:
`ERROR in ./app/AppWrapperSync.tsx:11
Module not found: Package path . is not exported from package C:\Users\marti\Desktop\TFG\Guaki\node_modules\realm (see exports field in C:\Users\marti\Desktop\TFG\Guaki\node_modules\realm\package.json)
9 |
10 | import {RealmProvider} from '@realm/react';
ERROR in ./app/models/Task.ts:9
Module not found: Package path . is not exported from package C:\Users\marti\Desktop\TFG\Guaki\node_modules\realm (see exports field in C:\Users\marti\Desktop\TFG\Guaki\node_modules\realm\package.json)
7 | // for an example of this.
8 |
ERROR in ./node_modules/@realm/react/dist/index.js 2:0-26
Module not found: Error: Package path . is not exported from package C:\Users\marti\Desktop\TFG\Guaki\node_modules\realm (see exports field in C:\Users\marti\Desktop\TFG\Guaki\node_modules\realm\package.json)
web compiled with 3 errors`
I've tried reinstalling realm, downgrading versions and creating a new project. Whatever i do the error shows up.
The text was updated successfully, but these errors were encountered: