Bump react-stripe-elements from 2.0.3 to 6.0.1

[dependabot-preview]

Bumps react-stripe-elements from 2.0.3 to 6.0.1.

Release notes

Sourced from react-stripe-elements's releases.

v6.0.1

Version bump that fixes some typos, no changes.

v6.0.0

New Features

• injectStripe now injects a reference to the Elements instance created by
  <Elements> as the prop elements.

The primary reason you would want an Elements instance is to use elements.getElement(), which provides an easy way to get a reference to an Element. You will need to get a reference to an Element to use confirmCardPayment, confirmCardSetup(), or createPaymentMethod().

Note that the old API for createPaymentMethod will continue to work and
provide automatic element injection, but we are updating documentation and
examples to use the new argument shape:

// old shape with automatic element detection - still works
this.props.stripe.createPaymentMethod('card').then(/* ... */);

// new shape without automatic element detection - recommended and 
// will work with new non-card PaymentMethods
this.props.stripe
  .createPaymentMethod({
    type: 'card',
    card: this.props.elements.getElement('card'),
  })
  .then(/* ... */);

Breaking Changes

• We have removed the getElement method on RSE components that we introduced
  in v5.1.0 in favor of the above change. Sorry for the churn.

v5.1.0

New Features

• Add support for accessing the underlying Element using refs via getElement.

Bug Fixes

• Fix crash when trying to create element while unmounting. Thanks @​CarsonF!

v5.0.1

Bug Fixes

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

v5.0.0

New Features

... (truncated)

Changelog

Sourced from react-stripe-elements's changelog.

v6.0.1 - 2019-11-13

Version bump that fixes some typos, no changes.

v6.0.0 - 2019-11-13

New Features

• injectStripe now injects a reference to the Elements instance created by
  <Elements> as the prop elements.

The primary reason you would want an Elements instance is to use
elements.getElement().
which provides an easy way to get a reference to an Element. You will need to
get a reference to an Element to use
confirmCardPayment,
confirmCardSetup(),
or
createPaymentMethod().

Note that the old API for createPaymentMethod will continue to work and
provide automatic element injection, but we are updating documentation and
examples to use the new argument shape:

// old shape with automatic element detection - still works
this.props.stripe.createPaymentMethod('card').then(/* ... */);

// new shape without automatic element detection - recommended and will work with new non-card PaymentMethods
this.props.stripe
  .createPaymentMethod({
    type: 'card',
    card: this.props.elements.getElement('card'),
  })
  .then(/* ... */);

Breaking Changes

• We have removed the getElement method on RSE components that we introduced
  in v5.1.0 in favor of the above change. Sorry for the churn.

v5.1.0 - 2019-10-22

New Features

• Add support for accessing the underlying Element using refs via getElement.

Bug Fixes

... (truncated)

Commits

• edaadf3 v6.0.1
• 91c465c Merge pull request #458 from stripe/dweedon/inject-elements
• 9580eea prettier
• f29ea72 updates to types, demos, and readme
• 6f24bd1 update docs and changelog
• 942f91e remove the RSE version of getElement
• 994a2e6 also inject elements into components wrapped in injectStripe
• 93e50bc Merge pull request #450 from stripe/mbarrett-update-fiddle
• c9b7d24 Update example fiddle link
• 173960c v5.1.0
• 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)

[dependabot-preview]

Superseded by #129.