@floating-ui/react-dom
2.1.9 · 11 Jul 2026MIT112.9M / weekRepositoryHomepagenpmAtom feed
Upgrading @floating-ui/react-dom From 0.1.2 to 2.1.9
49 releases in betweennotes for 48
- 10+
- changes to make
- 0
- advisories fixed
- 16+
- new
- 24+
- fixes
Counted from 48 of 49 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- breaking2.0.0
- breaking2.0.0
- breaking2.0.0
- breaking1.0.0
- breaking1.0.0
- breaking1.0.0
- breaking1.0.0
- breaking1.0.0
- breaking1.0.0
- breaking0.3.4
Release by release
- fixed
Support explicit
undefinedfor optional properties withexactOptionalPropertyTypes
- fixed
- fixed
react: Avoid duplicate
optionskey warning in reactive middleware wrappers
- fixed
2.1.4 – 2.1.74 releases, nothing new or fixed in the notes
- fixed
useFloating: Correct
transformdefault doc (@default trueinstead of@default false)
- fixed
- fixed
useFloating: Avoid setting
isPositionedto true whenopenis false
- fixed
2.1.1nothing new or fixed in the note
- new
Support dependency array as a second argument of all middleware. This ensures stateful options can be kept reactive when making them derived (passing a function that returns the options):
- new
- fixed
types: Replace
React_2withReactin generated .d.ts files
- fixed
21 other lines we could not sort, mostly version bumps
- 1.0.1
Minor perf improvement of
arrowmodifier - 1.0.0
Converted source code to ES6
- 1.0.0
Build now uses Rollup
- 1.0.0
Moved from JSHint to ESLint
- 1.0.0
Moved from Uglify to Babili
- 1.0.0
Get rid of Grunt
- 1.0.0
Updated npm dependencies
- 1.0.0
Full support for HTML5 shadow root and HTML5 components (#88) (thanks @nadiam84)
- 1.0.0
Improved flip detection strategy (#82) (thanks @nadiam84)
- 1.0.0
You can now set attributes defining them in
data.attributes, properties withfalsevalues will be removed
15 internal lines (docs, tests, tooling) left out.