Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added bun.lockb
Binary file not shown.
8 changes: 5 additions & 3 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,10 @@
"typescript": "^5.2.2"
},
"peerDependencies": {
"expo": "*",
"react": "*",
"react-native": "*"
}
"react-native": "*",
"expo": "*",
"expo-modules-core": "*"
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unsure if expo-modules-core needs to be listed as a peer dependency, gotta checkout expo docs!

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, expo-modules-core should not be listed as peer dependency and also imports like requireNativeModule, which used to be imported from expo-modules-core should be imported from expo. It used to be from expo-modules-core, but that changed since SDK 51 I think.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked, the implementation is definitely outdated:

import { requireNativeModule } from "expo-modules-core";

},
"packageManager": "[email protected]"
}
Loading