Bump mobx-react from 5.3.6 to 5.4.4

[dependabot-preview]

Bumps mobx-react from 5.3.6 to 5.4.4.

Changelog

Sourced from mobx-react's changelog.

MobX-React Changelog

6.1.2 / 6.1.3

• Add reexport of useObserver from mobx-react-lite #734
• Add the ability to pass multiple children to Provider
• Fixed #717. Now inject works correctly with components that use React.forwardRef
• Observer checks for use of React.memo #720
• Get rid of the redundant Injector wrapper #716

6.1.1

• Fixed issue where combining @disposeOnUnmount with disposeOnUnmount didn't clean up everything. Fixes #666 trough #671 by @​JabX

6.1.0

• Restored the classic implementation of observer: class based components are patched again, rather than wrapping them in <Observer>, see #703. Fixes:
  • componentDidUpdate not being triggered after a reactive render #692
  • The appearance of an additional <Observer> component in the component tree, which complicates shallow testing #699
  • Some regressions in disposeOnUnmount #702
  • Note that dev tool support, and other constraints mentioned in the 6.0.0 release notes have not been restored.
• The function useStaticRendering(value: boolean): void from mobx-react-lite is now exposed

6.0.4

• Fixed IE 11 compatibility which was accidentally broken. Fixes #698

6.0.3

• disposeOnUnmount now supports initializing it with an array of disposers. Fixes #637 through #641 by @​Amareis
• Fixed hoisting of statically declared members. Fixes #678 through #682 by @​meabed

6.0.2

• Added missing types for MobXProviderContext, useLocalStore and useAsObservableSource. Fixes #679.

6.0.0

Breaking changes

• The minimal supported version of React is 16.8.0
• Killed the possibility to directly pass store names to observer. Always use inject instead. (This was deprecated for a long time already). observer(["a", "b"], component) should now be written as inject("a", "b")(component).
• observer components no longer automatically recover from errors (to prevent potential memory leaks). Instead, this is the responsibility of error boundaries.
• inject now supports ref forwarding. As such, the .wrappedInstance property has been removed since refs can be used instead. (Fixes #616 (See also #619 by 42shadow42)
• Changing the set of stores in Provider is no longer supported and while throw a hard error (this was a warning before), as the model of Provider / inject has always been designed to inject final values into the tree. (That is, constanted references, the injected objects themselves can be stateful without problem). If you want to dynamically swap what is provided into the tree, use React.createContext instead of Provider / inject. The suppressChangedStoreWarningflag forProvider` has been dropped.
• The third argument of custom storesToProps functions passed to inject is no longer available.
• <Observer> no longer supports the deprecated inject property.
• Defining shouldComponentUpdate on observer based components is no longer supported
• propTypes is no longer exposed, use PropTypes instead
• disposeOnUnmount now only supports direct subclasses of React.Component and React.PureComponent. This prevents several unreliable edge cases that silently leaked memory before. Either only extend React.(Pure)Component when using disposeOnUnmount, or manually clean up stuff in componentWillUnmount.

... (truncated)

Commits

• 20ed293 Published version 5.4.4
• 1e8d6b5 Merge pull request #632 from WearyMonkey/WearyMonkey-patch-1
• 55eeb96 Fix disposeOnUmount typo in README.md
• 75274c8 Merge pull request #631 from henning-kvinnesland/patch-1
• e54e10e Fix typo!
• 02040b0 Merge pull request #618 from fi3ework/master
• 34b34db Merge pull request #622 from normano64/cache-symbols
• 312070a Merge pull request #623 from jamonholmgren/patch-1
• 7266e1a Adds Ignite Bowser boilerplate
• 68f92ac fix: build after new version is set in publish flow
• Additional commits viewable in compare view

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.