[Snyk] Upgrade recoil from 0.6.1 to 0.7.4

[snyk-bot]

Snyk has created this PR to upgrade recoil from 0.6.1 to 0.7.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 8 versions ahead of your current version.
• The recommended version was released a month ago, on 2022-06-22.

Release notes

Package name: recoil

• 0.7.4 - 2022-06-22
  
  • Fix missing Flow types (#1857)
  • Cleanup memory leak when using atoms with selector defaults. (#1821, #1840, #1844)
• 0.7.3 - 2022-06-02
  
  • Enable atoms and selectors to be used in family parameters (#1172)
  • Add parentStoreID_UNSTABLE to atom effects which is the ID of the parent store it cloned from, such as the host <RecoilRoot> store for useRecoilCallback() snapshots. (#1744)
  • Atom effects can initialize or set atoms to wrapped values (#1681)
• 0.7.3-alpha.2 - 2022-05-09
• 0.7.3-alpha.1 - 2022-05-06
• 0.7.3-alpha - 2022-05-06
• 0.7.2 - 2022-04-14
  
  • Selector cache lookup optimizations (#1720, #1736)
  • Allow async selectors to re-evaluate when async dependencies are discovered with stale state (#1736)
• 0.7.1 - 2022-04-13
  

  Typing

  • Add explicit children prop to <RecoilRoot> and useRecoilBridgeAcrossReactRoots_UNSTABLE() for TypeScript for @ types/react with React 18 (#1718, #1717, #1726, #1731)
  • Update typing for family parameters to better support Map, Set, and classes with toJSON(). (#1709, #1703)

  Fixes

  • Avoid dev-mode console error with React 18 when using shared async selectors across multiple <RecoilRoot>'s. (#1712)
  • Cleanup potential memory leak when using async selectors. (#1714)
  • Fix potentially hung async selectors when shared across multiple roots that depend on atoms initialized with promises that don't resolve. (#1714)
• 0.7.0 - 2022-04-01
  

  New Features

  • The default value is now optional for atom() and atomFamily(). If not provided the atom will initialize to a pending state. (#1639)
  • Add getStoreID() method to Snapshot (#1612)
  • Publish RecoilLoadable.loading() factory for making an async Loadable which never resolves. (#1641)

  Breaking Changes

  • Selector's get() and Atom's default can now accept a Loadable to put the node in that state. If you wish to store a Loadable, Promise, or RecoilValue directly you can wrap it with selector.value() or atom.value(). (#1640)
  • useRecoilCallback() now provides a snapshot for the latest state when the callback is called instead of the latest rendered state, which had issues (#1610, #1604)

  Improvements / Optimizations

  • Automatically retain snapshots for the duration of async callbacks. (#1632)
  • Optimization for more selector dependencies. 2x improvement with 100 dependencies, 4x with 1,000, and now able to support 10,000+. (#1651, #1515, #914)
  • Better error reporting when selectors provide inconsistent results (#1696)

  Fixes

  • Avoid spurious console errors from effects when calling setSelf() from onSet() handlers. (#1589, #1582)
  • Freezing user values in dev mode now works in JS environments without the Window interface. (#1571)
• 0.6.1 - 2022-01-29
  

  Fix postInstall script

from recoil GitHub release notes

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs