fix: async-storage as optional peer dependency

[oscb]

• Makes @react-native-async-storage/async-storage and react-native-get-random-values as peer dependencies, async-storage is now optional in both core and sovran. PR by: @mateusz1913
• Remove sovran type exports. PR by: @danychi
• Fixing jest setup for tests for mocking UUID and react-native-get-random-values for all tests by default.
• Fixed the async-storage mock

Co-authored-by: Mateusz Mędrek [email protected]
Co-authored-by: Daniel Alarcón Amador [email protected]

[isaachinman]

Thanks @oscb – this is a fantastic improvement/re-organisation. Any idea when we can expect a release? Will this be a major release and/or require a minimum RN version?

[oscb]

@isaachinman should be out before the end of the week! Quite possibly today or tomorrow if we can merge all fixes we want to go along with this change

[oscb]

🎉 This PR is included in version @segment/sovran-react-native-v1.0.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-v2.13.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-adjust-v0.6.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-advertising-id-v1.2.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-amplitude-session-v0.3.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-appsflyer-v0.5.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-branch-v1.0.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-braze-middleware-v1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-braze-v0.5.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-destination-filters-v1.0.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-facebook-app-events-v0.5.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[Alex-McLean]

@oscb was @segment/sovran-react-native intentionally release as 1.0.1, rather than 0.4.6 or even 0.5.0?

If it is intended to be a minor or major patch, then my understanding is there is also a required change to the core library's dependencies, as it is still listed as "@segment/sovran-react-native": "^0.4.5" here.

Am currently trying to include this fix in my repo, but analytics-react-native will still only resolve to the old 0.4.5.

[isaachinman]

@Alex-McLean @oscb Same issue here. Setting resolutions works as a temporary fix:

"resolutions": {
  "@segment/sovran-react-native": ">=1.0.1"
}

Clearly this shows that the repo is missing any sort of functional testing in its deploy/release pipeline.

[oscb]

@Alex-McLean yea, that was a mistake. It is the first release of that package from this monorepo, so npm version bumped the major version unexpectedly. Just released a fix in v2.13.3 to fix the dependency version in the core package

@isaachinman the monorepo does run functional integration tests against the example app, but it uses module resolutions to resolve and test the code to the commit being released. I'm guessing we could bump versions and deploy to a local registry, then install dependencies from there so that we could spot version bump mismatches before actually releasing to the public NPM Registry, but curious if you have any suggestions.

[isaachinman]

Thanks @oscb for a quick fix!

The workflow you are describing with either a local registry, or canary versions on a remote registry, sounds like the right approach to me.

I'd highly suggest having a look at auto if you're not already aware of it.

[oscb]

🎉 This PR is included in version @segment/analytics-react-native-plugin-idfa-v0.6.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀