Bump react-stripe-elements from 2.0.3 to 3.0.1

[dependabot-preview]

Bumps react-stripe-elements from 2.0.3 to 3.0.1.

Release notes

Sourced from react-stripe-elements's releases.

v3.0.1

Bug Fixes

• Fixes a bug where calling stripe.createPaymentMethod would error in IE.

v3.0.0

New Features

• added a changelog
• added support for stripe.handleCardPayment and stripe.createPaymentMethod.
  These methods allow you to easily integrate Stripe's new Payment Intents API.
  Like createToken and createSource, these new methods will automatically
  find and use a corresponding Element when they are called.

    stripe.createPaymentMethod(
      paymentMethodType: string,
      paymentMethodDetails: Object
    ): Promise<{error?: Object, paymentIntent?: Object}>
  
    stripe.handleCardPayment(
      clientSecret: string,
      paymentMethodDetails: Object
    ): Promise<{error?: Object, paymentIntent?: Object}>

  For more information, please review the Stripe Docs:
  • stripe.createPaymentMethod
  • stripe.handleCardPayment
  • Payment Intents API
  • Payment Methods API

Breaking Changes:

• If you were already using handleCardPayment or createPaymentMethod with
  react-stripe-elements, you should upgrade your integration. These methods
  will now automatically find and use valid Elements.

  Old Way

  <CardElement
    ...
    onReady={this.handleReady}
  />
  
  handleReady = (element) => {
    this.setState({cardElement: element}) ;
  };
  
  let { paymentIntent, error } = await this.props.stripe.handleCardPayment(
    intent.client_secret, this.state.cardElement, {}
  );

  New Way

... (truncated)

Changelog

Sourced from react-stripe-elements's changelog.

Changelog

react-stripe-elements adheres to
Semantic Versioning.

v5.0.1 - 2019-09-18

Bug Fixes

• Fixes a bug where calling stripe.createPaymentMethod would error in IE.

v5.0.0 - 2019-08-27

New Features

• React 16.9 compatibility.

Breaking Changes

• We replaced the internal use of deprecated componentWillReceiveProps. This
  internal movement of logic between lifecycle methods is likely safe for almost
  all apps and should not require any changes.

v4.0.1 - 2019-08-14

Bug Fixes

• Fixes a bug where calling stripe.handleCardPayment with only a client secret
  caused an error to be thrown.

v4.0.0 - 2019-07-05

New Features

• Renamed CardCVCElement to CardCvcElement which better mirrors the Elements
  API. We will keep the old component name around as an alias until 5.0.0.

• Added support for stripe.handleCardSetup

    stripe.handleCardSetup(
      clientSecret: string,
      data?: Object
    ): Promise<{error?: Object, setupIntent?: Object}>

  For more information, please review the Stripe Docs:

  • stripe.handleCardSetup

Deprecations

... (truncated)

Commits

• 0404d9c v3.0.1
• f2693ea Merge pull request #432 from stripe/v3-fix-cpm-ie
• 5e8ef50 fix createPaymentMethod in ie
• 6743db5 v3.0.0
• 918a900 Merge pull request #347 from stripe/v3.0
• 0144400 Merge pull request #345 from stripe/payment-intents
• 46d9c13 more clarity in changelog
• 47b214b Merge branch 'v3.0' into payment-intents
• 24af7c4 requested changes
• f1d40bd add changelog to changelog
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by dweedon-stripe, a new releaser for react-stripe-elements since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[dependabot-preview]

Superseded by #82.