Describe the bug
I'm having an issue when I'm trying to update an app (Expo) to the 2.4.0 release from the 2.3.0.
The errors come from the fact that the async-local-storage peerDependency was changed to: @react-native-community/async-storage.
If I fork the package locally, revert this change (back to @react-native-async-storage/async-storage) and the respective requires on the Meteor.js file, it works without a problem.
Looking at the npm page of the community version, it was moved to this organization: Async Storage has moved to new organization: https://github.com/react-native-async-storage/async-storage, which is the one the package was using.
What's the reason for this change in specific? Is it something we can easily just revert?
I think this works on bare react-native flows, but I haven't checked.
Describe the bug
I'm having an issue when I'm trying to update an app (
Expo) to the2.4.0release from the2.3.0.The errors come from the fact that the
async-local-storage peerDependencywas changed to:@react-native-community/async-storage.If I fork the package locally, revert this change (back to
@react-native-async-storage/async-storage) and the respective requires on theMeteor.jsfile, it works without a problem.Looking at the npm page of the
communityversion, it was moved to this organization:Async Storage has moved to new organization: https://github.com/react-native-async-storage/async-storage, which is the one the package was using.What's the reason for this change in specific? Is it something we can easily just revert?
I think this works on bare
react-nativeflows, but I haven't checked.