Update memoize-one related packages

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@types/memoize-one	devDependencies	patch	^4.1.0 -> ^4.1.1
memoize-one	dependencies	minor	^5.0.0 -> ^5.1.1

---

Release Notes

alexreardon/memoize-one

v5.1.1

Compare Source

Looser EqualityFn type

For 5.1.0 we shipped an EqualityFn type that was not ideal. It was decided that the simplest path forward for consumers was to move to a looser EqualityFn type. #​73

- export type EqualityFn = (newArgs: readonly unknown[], lastArgs: readonly unknown[]) => boolean;
+ export  type EqualityFn = (newArgs: any[], lastArgs: any[]) => boolean;

Thanks @​SanderDeWaal1992 for raising this issue

v5.1.0

Compare Source

Typescript support! 🤘🤩🤘

Typescript consumers will now start getting correct types without having to rely on installing @types/memoize-one. Internally memoize-one is now authored in Typescript.

memoize-one is still shipping flow types, so if you are using, or want to use flow, then you will still get the same fantastic types you always have.

And if you want to use good old regular vanilla JS then you can do that too!

This change has been marked as a feature release as it will not break any existing flow consumers

❤ Thanks to @​PavelVanecekAtlassian, @​danieldelcore and @​TrySound for their assistance. And thanks to @​karol-majewski and @​franklixuefei for creating the previous memoize-one typescript types on DefinitelyTyped

v5.0.5

Compare Source

• Naming functions for better stack traces #​68
• Bumping all dev dependencies #​68
• Bumping node for travis build and adding .nvm file #​69

v5.0.4

Compare Source

😢 Unwinding: Improved typing #​61

This change broke existing flow type consumers. We need to look into how our local flow type tests did not pick this up. For now, the flow change has been reverted. If we do move to the new flow types then we will need to publish a good upgrade story.

v5.0.3

Compare Source

⚠️ This release has been deprecated on npm. However, all improvements are available in 5.0.4. There were some issues with the updated flow types

🚀 Performance #​59

We tweaked our default equality function to run much faster.

From 1.1 to 15.5 times faster!

Target	Change
Node 8.11.3	1450% faster (8 million ops/sec => 124 million ops/sec)
Node 11.12	23% faster
Chrome (latest)	10% faster
Safari (latest)	50% faster
Firefox (latest)	10% faster

Thanks to @​wbinnssmith for creating performance benchmarks to test ideas #​62. Thanks @​theKashey for your input!

👩‍⚕️ Improved typing #​61

Removed in 5.0.4

Thanks to @​wbinnssmith we now have even better flow typing.

Other

• Upgrading to flow 0.96 #​63

v5.0.2

Compare Source

• Fixing flow issue #​58. Caused by using non-standard $ExpectError comment. Thanks @​jmansor for the pick up

v5.0.1

Compare Source

Engineering health

• Bumping all dev dependencies #​56
• Upgrading to flow 0.95.1 #​56
• Minor internal cleanup of flow types #​56

Other

• Improving language used for argument length checking for the default equality function in the docs #​56

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

Newsflash: Renovate has joined WhiteSource, and is now free for all use. Learn more or view updated terms and privacy policies.

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e8592f1

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[spalger]

7.x/7.6: e2349b0