@shopify/checkout-sheet-kit

[markmur]

What are you trying to accomplish?

• Update documentation
• Rename module (react-native-shopify-checkout-kit → @shopify/checkout-sheet-kit)
• Update names of exports
  • ShopifyCheckoutKit → ShopifyCheckoutSheet
  • useShopifyCheckoutKit → useShopifyCheckoutSheet
  • ShopifyCheckoutKitProvider → ShopifyCheckoutSheetProvider
• Update name in package.json
• Update exported modules for iOS
• Update exported modules for Android
• Update tests
• Update all import references in the sample app
• Update all module usage in the sample app

Before you deploy

• I have added tests to support my implementation
• I have read and agree with the contributing documentation readme
• I have read and agree with the code of conduct documentation readme
• I have updated any documentation related to these changes.
• I have updated the README.

[caution-tape-bot]

👋 It looks like you're updating JavaScript packages that are known
to cause problems when duplicated.

You can deduplicate them with the yarn-deduplicate utility:

npx yarn-deduplicate --packages graphql react react-dom webpack
npx yarn-deduplicate --scopes @shopify @apollo

If running these commands doesn't produce a change in your yarn.lock file,
you didn't have duplications in these packages and can carry on.

A duplicate React version may cause an invalid hook call warning.

React context providers usually use module-scoped globals as their
default context values. Multiple versions of such packages will yield
multiple global instances, resulting in oblique runtime errors.

---

This comment was added by the YarnLock::DupeWarning Caution Tape Bot rule.
View the source of this rule in Services DB

[cianbuckley]

LGTM