build(deps): bump react-resizable-panels from 1.0.10 to 2.0.19

[dependabot]

Bumps react-resizable-panels from 1.0.10 to 2.0.19.

Release notes

Sourced from react-resizable-panels's releases.

2.0.17

• Prevent pointer events handled by resize handles from triggering elements behind/underneath (#338)

2.0.16

• Replaced .toPrecision() with .toFixed() to avoid undesirable layout shift (#323)

2.0.15

• Better account for high-precision sizes with onCollapse and onExpand callbacks (#325)

2.0.14

• Better account for high-precision collapsedSize values (#325)

2.0.13

• Fix potential cycle in stacking-order logic for an unmounted node (#317)

2.0.12

• Improve resize for edge cases with collapsed panels; intermediate resize states should now fall back to the most recent valid layout rather than the initial layout (#311)

2.0.11

• Fix resize handle cursor hit detection when when viewport is scrolled (#305)

2.0.10

• Fix conditional layout edge case (#309)

2.0.9

• Fix Flex stacking context bug (#301)
• Fix case where pointer event listeners were sometimes added to the document unnecessarily

2.0.7

• Group default layouts use toPrecision to avoid small layout shifts due to floating point precision differences between initial server rendering and client hydration (#295)

2.0.6

• Replace useLayoutEffect usage with SSR-safe wrapper hook (#294)

2.0.5

• Resize handle hit detection considers stacking context when determining hit detection (#291)

2.0.4

• Fixed PanelResizeHandle onDragging prop to only be called for the handle being dragged (#289)

2.0.3

• Fix resize handle onDragging callback (#278)

2.0.2

• Fixed an issue where size might not be re-initialized correctly after a panel was hidden by the unstable_Activity (previously "Offscreen") API.

2.0.1

• Fixed a regression introduced in 2.0.0 that caused React onClick and onMouseUp handlers not to fire.

2.0.0

... (truncated)

Commits

• 8f89ea8 2.0.18 -> 2.0.19
• 4714370 Add optional 'minSize' override param to panel 'expand' imperative API (#347)
• 634284b 2.0.17 -> 2.0.18
• ae82c4f Inline object hitAreaMargins should not trigger re-initialization
• 638d0f6 2.0.16 -> 2.0.17
• a756ba3 v2.0.16 (#339)
• d712d21 Prevent pointer events from triggering on elements behind hitAreaMargins (#338)
• 8b049a6 docs: Update README.md (#332)
• 641e8dc remove stray 'v' character (#330)
• d6d680f Add installation instructions for pnpm and bun (#327)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[changeset-bot]

⚠️ No Changeset found

Latest commit: e5a5bb9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR