npm / @dnd-kit/abstract
@dnd-kit/abstract
What changed in @dnd-kit/abstract 0.4 to 0.5, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-21.
5 breaking4 new APIs and options5 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@dnd-kit/abstract 0.53 changes
New APIs and options 1
Adds a getter to the drag operation status.
Fixes and other changes 2
Fixes stale initialIndex and initialGroup values in onBeforeDragStart after the item has moved.
The return type of the plugin configurator now supplies the correct Options type.
@dnd-kit/abstract 0.411 changes
Breaking changes 5
Provides event handler signatures, replacing use of DragDropEvents for typing event handlers.
Provides a mapping from event names to event object types, replacing use of DragDropEvents for typing event objects.
The ambiguous type is replaced by DragDropEventMap for event objects and DragDropEventHandlers for handler signatures.
The feedback setting moves from the Draggable entity to Feedback plugin configuration.
When an element is both draggable and droppable, onDragStart now fires before onDragOver.
New APIs and options 3
Drop animation can be configured per-draggable through Feedback plugin configuration.
Plugins can read per-entity options through source.pluginConfig(PluginClass).
Draggable entities accept per-entity plugin configuration using the existing Plugin.configure() pattern; listed plugins are registered on the manager if needed.
Fixes and other changes 3
Entity id changes are deferred to a microtask and flushed atomically, preventing collision oscillation and cleaning up stale registry entries.
Deduplicating configured plugins no longer moves them to the end of the registration list, preserving dependencies such as Feedback resolving StyleInjector during construction.
The type of the source.data object is inferred from its type argument.