fix: improve falsy value handling

[atomiks]

No description provided.

[rollingversions]

@floating-ui/core (1.0.1 → 1.0.2)

Bug Fixes

• fix: if the reference or floating elements are falsy/null when computePosition() is called there's an unhelpful error about getComputedStyle; there is now a proper error message in dev mode.

• fix: the middleware array can now contain false, null, or undefined values. This enables you to pass conditional middleware inline without needing a verbose spread ...(cond ? [m()] : []) or separate statements like .push() — at least for TypeScript, as you could already filter it manually externally.

  middleware: [
    shouldFlip && flip(),  
    arrowElement && arrow({ element: arrowElement }),
  ]

@floating-ui/dom (1.0.4 → 1.0.5)

Bug Fixes

• fix: support falsy values in middleware option for conditionals

@floating-ui/react-dom (1.0.0 → 1.0.1)

Bug Fixes

• fix: support falsy values in middleware option for conditionals

@floating-ui/react-dom-interactions (0.10.3 → 0.10.4)

Bug Fixes

• fix: support falsy values in middleware option for conditionals

@floating-ui/react-native (0.8.0 → 0.8.1)

Bug Fixes

• fix: support falsy values in middleware option for conditionals

Edit changelogs

[netlify]

✅ Deploy Preview for vibrant-gates-22c214 canceled.

Name	Link
🔨 Latest commit	f8aa6e8
🔍 Latest deploy log	https://app.netlify.com/sites/vibrant-gates-22c214/deploys/636fb2dd4d725200093df954