react-draggable vs react-dnd vs react-beautiful-dnd vs @hello-pangea/dnd
React Drag-and-Drop Libraries Comparison
1 Year
react-draggablereact-dndreact-beautiful-dnd@hello-pangea/dndSimilar Packages:
What's React Drag-and-Drop Libraries?

Drag-and-drop libraries for React provide developers with tools to implement drag-and-drop functionality in their applications. These libraries abstract the complexities of handling mouse events, touch events, and state management, allowing developers to create interactive and user-friendly interfaces. They cater to various use cases, from simple draggable components to complex nested drag-and-drop interfaces, enhancing user experience by allowing intuitive manipulation of UI elements.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
react-draggable2,498,5979,140244 kB2452 years agoMIT
react-dnd2,331,80121,345231 kB463-MIT
react-beautiful-dnd1,845,29133,7901.39 MB644-Apache-2.0
@hello-pangea/dnd556,5133,0521.26 MB992 months agoApache-2.0
Feature Comparison: react-draggable vs react-dnd vs react-beautiful-dnd vs @hello-pangea/dnd

Complexity and Use Cases

  • react-draggable:

    react-draggable is best for simple drag-and-drop scenarios, focusing on moving elements without complex interactions. It is lightweight and straightforward, making it ideal for applications that only need basic draggable functionality.

  • react-dnd:

    react-dnd offers a highly customizable architecture, allowing developers to create intricate drag-and-drop interfaces. It is suitable for applications that need advanced features and flexibility in handling drag-and-drop interactions.

  • react-beautiful-dnd:

    react-beautiful-dnd supports complex use cases, including nested lists and dynamic content. It provides a rich set of features, making it suitable for applications that require a polished user experience and advanced drag-and-drop interactions.

  • @hello-pangea/dnd:

    @hello-pangea/dnd is designed for simplicity and ease of use, making it suitable for basic drag-and-drop features without overwhelming complexity. It is ideal for projects that require quick implementation without extensive customization.

Performance

  • react-draggable:

    react-draggable is lightweight and performs well in simple scenarios. It is suitable for applications that require minimal drag-and-drop functionality without performance concerns.

  • react-dnd:

    react-dnd allows for fine-tuned performance optimizations, enabling developers to manage rendering and updates effectively. It is ideal for complex applications where performance is a key concern and customization is necessary.

  • react-beautiful-dnd:

    react-beautiful-dnd is designed with performance in mind, but its extensive features may introduce some overhead. It is best used in applications where the user experience is paramount, and the benefits of its features outweigh potential performance costs.

  • @hello-pangea/dnd:

    @hello-pangea/dnd is optimized for performance, providing a lightweight solution that minimizes overhead. It is suitable for applications where performance is critical and simplicity is desired.

Accessibility

  • react-draggable:

    react-draggable has basic accessibility support, but developers may need to add enhancements for full compliance. It is best for simple applications where accessibility is not a primary concern.

  • react-dnd:

    react-dnd allows developers to implement custom accessibility features, giving flexibility in how drag-and-drop interactions are handled. It is suitable for applications where accessibility is a priority and customization is needed.

  • react-beautiful-dnd:

    react-beautiful-dnd places a strong emphasis on accessibility, providing built-in support for keyboard navigation and screen readers. It is ideal for applications that prioritize inclusive design and user accessibility.

  • @hello-pangea/dnd:

    @hello-pangea/dnd provides basic accessibility features, but developers may need to implement additional enhancements for full compliance. It is suitable for projects that require a quick solution without extensive accessibility considerations.

Learning Curve

  • react-draggable:

    react-draggable is straightforward and easy to learn, making it ideal for beginners or those needing simple drag-and-drop functionality without a steep learning curve.

  • react-dnd:

    react-dnd has a steeper learning curve, requiring a deeper understanding of its concepts and architecture. It is suitable for experienced developers looking to implement advanced drag-and-drop functionality.

  • react-beautiful-dnd:

    react-beautiful-dnd has a moderate learning curve due to its rich feature set and API. It is best for developers who are willing to invest time in understanding its capabilities for more complex applications.

  • @hello-pangea/dnd:

    @hello-pangea/dnd has a gentle learning curve, making it easy for developers to get started quickly. It is suitable for those who want to implement drag-and-drop features without extensive prior knowledge.

Customization and Extensibility

  • react-draggable:

    react-draggable offers basic customization options, making it suitable for simple use cases where extensive customization is not necessary.

  • react-dnd:

    react-dnd excels in customization and extensibility, enabling developers to create complex interactions and integrate with other libraries. It is suitable for applications that require a high degree of flexibility.

  • react-beautiful-dnd:

    react-beautiful-dnd provides a range of customization options, allowing developers to tailor the drag-and-drop experience to their needs. It is ideal for applications that require a polished and customizable user interface.

  • @hello-pangea/dnd:

    @hello-pangea/dnd offers limited customization options, focusing on simplicity. It is suitable for projects that do not require extensive customization.

How to Choose: react-draggable vs react-dnd vs react-beautiful-dnd vs @hello-pangea/dnd
  • react-draggable:

    Use react-draggable for simple drag-and-drop scenarios where you only need to move elements around without the complexity of a full drag-and-drop interface. It is lightweight and easy to implement, making it perfect for straightforward applications that require basic draggable functionality.

  • react-dnd:

    Opt for react-dnd if you need a highly customizable drag-and-drop solution that allows for complex interactions and integrations with other libraries. It is ideal for applications that require a flexible architecture and advanced features like drag previews and drop targets, making it suitable for more sophisticated use cases.

  • react-beautiful-dnd:

    Select react-beautiful-dnd for a comprehensive and feature-rich drag-and-drop solution that supports complex use cases, such as nested lists and dynamic content. It is well-suited for applications that require a polished user experience and accessibility features, although it may have a steeper learning curve due to its extensive API.

  • @hello-pangea/dnd:

    Choose @hello-pangea/dnd if you need a lightweight and straightforward solution for implementing drag-and-drop features with a focus on performance and simplicity. It is a fork of react-beautiful-dnd and is ideal for projects that require minimal setup and quick integration.

README for react-draggable

React-Draggable

TravisCI Build Status Appveyor Build Status npm downloads gzip size version

A simple component for making elements draggable.

<Draggable>
  <div>I can now be moved around!</div>
</Draggable>

|Version | Compatibility| |------------|--------------| |4.x | React 16.3+ | |3.x | React 15-16 | |2.x | React 0.14 - 15 | |1.x | React 0.13 - 0.14 | |0.x | React 0.10 - 0.13 |


Technical Documentation

Installing

$ npm install react-draggable

If you aren't using browserify/webpack, a UMD version of react-draggable is available. It is updated per-release only. This bundle is also what is loaded when installing from npm. It expects external React and ReactDOM.

If you want a UMD version of the latest master revision, you can generate it yourself from master by cloning this repository and running $ make. This will create umd dist files in the dist/ folder.

Exports

The default export is <Draggable>. At the .DraggableCore property is <DraggableCore>. Here's how to use it:

// ES6
import Draggable from 'react-draggable'; // The default
import {DraggableCore} from 'react-draggable'; // <DraggableCore>
import Draggable, {DraggableCore} from 'react-draggable'; // Both at the same time

// CommonJS
let Draggable = require('react-draggable');
let DraggableCore = Draggable.DraggableCore;

<Draggable>

A <Draggable> element wraps an existing element and extends it with new event handlers and styles. It does not create a wrapper element in the DOM.

Draggable items are moved using CSS Transforms. This allows items to be dragged regardless of their current positioning (relative, absolute, or static). Elements can also be moved between drags without incident.

If the item you are dragging already has a CSS Transform applied, it will be overwritten by <Draggable>. Use an intermediate wrapper (<Draggable><span>...</span></Draggable>) in this case.

Draggable Usage

View the Demo and its source for more.

import React from 'react';
import ReactDOM from 'react-dom';
import Draggable from 'react-draggable';

class App extends React.Component {

  eventLogger = (e: MouseEvent, data: Object) => {
    console.log('Event: ', e);
    console.log('Data: ', data);
  };

  render() {
    return (
      <Draggable
        axis="x"
        handle=".handle"
        defaultPosition={{x: 0, y: 0}}
        position={null}
        grid={[25, 25]}
        scale={1}
        onStart={this.handleStart}
        onDrag={this.handleDrag}
        onStop={this.handleStop}>
        <div>
          <div className="handle">Drag from here</div>
          <div>This readme is really dragging on...</div>
        </div>
      </Draggable>
    );
  }
}

ReactDOM.render(<App/>, document.body);

Draggable API

The <Draggable/> component transparently adds draggability to its children.

Note: Only a single child is allowed or an Error will be thrown.

For the <Draggable/> component to correctly attach itself to its child, the child element must provide support for the following props:

  • style is used to give the transform css to the child.
  • className is used to apply the proper classes to the object being dragged.
  • onMouseDown, onMouseUp, onTouchStart, and onTouchEnd are used to keep track of dragging state.

React.DOM elements support the above properties by default, so you may use those elements as children without any changes. If you wish to use a React component you created, you'll need to be sure to transfer prop.

<Draggable> Props:

//
// Types:
//
type DraggableEventHandler = (e: Event, data: DraggableData) => void | false;
type DraggableData = {
  node: HTMLElement,
  // lastX + deltaX === x
  x: number, y: number,
  deltaX: number, deltaY: number,
  lastX: number, lastY: number
};

//
// Props:
//
{
// If set to `true`, will allow dragging on non left-button clicks.
allowAnyClick: boolean,

// Determines which axis the draggable can move. This only affects
// flushing to the DOM. Callbacks will still include all values.
// Accepted values:
// - `both` allows movement horizontally and vertically (default).
// - `x` limits movement to horizontal axis.
// - `y` limits movement to vertical axis.
// - 'none' stops all movement.
axis: string,

// Specifies movement boundaries. Accepted values:
// - `parent` restricts movement within the node's offsetParent
//    (nearest node with position relative or absolute), or
// - a selector, restricts movement within the targeted node
// - An object with `left, top, right, and bottom` properties.
//   These indicate how far in each direction the draggable
//   can be moved.
bounds: {left?: number, top?: number, right?: number, bottom?: number} | string,

// Specifies a selector to be used to prevent drag initialization. The string is passed to
// Element.matches, so it's possible to use multiple selectors like `.first, .second`.
// Example: '.body'
cancel: string,

// Class names for draggable UI.
// Default to 'react-draggable', 'react-draggable-dragging', and 'react-draggable-dragged'
defaultClassName: string,
defaultClassNameDragging: string,
defaultClassNameDragged: string,

// Specifies the `x` and `y` that the dragged item should start at.
// This is generally not necessary to use (you can use absolute or relative
// positioning of the child directly), but can be helpful for uniformity in
// your callbacks and with css transforms.
defaultPosition: {x: number, y: number},

// If true, will not call any drag handlers.
disabled: boolean,

// Specifies the x and y that dragging should snap to.
grid: [number, number],

// Specifies a selector to be used as the handle that initiates drag.
// Example: '.handle'
handle: string,

// If desired, you can provide your own offsetParent for drag calculations.
// By default, we use the Draggable's offsetParent. This can be useful for elements
// with odd display types or floats.
offsetParent: HTMLElement,

// Called whenever the user mouses down. Called regardless of handle or
// disabled status.
onMouseDown: (e: MouseEvent) => void,

// Called when dragging starts. If `false` is returned any handler,
// the action will cancel.
onStart: DraggableEventHandler,

// Called while dragging.
onDrag: DraggableEventHandler,

// Called when dragging stops.
onStop: DraggableEventHandler,

// If running in React Strict mode, ReactDOM.findDOMNode() is deprecated.
// Unfortunately, in order for <Draggable> to work properly, we need raw access
// to the underlying DOM node. If you want to avoid the warning, pass a `nodeRef`
// as in this example:
//
// function MyComponent() {
//   const nodeRef = React.useRef(null);
//   return (
//     <Draggable nodeRef={nodeRef}>
//       <div ref={nodeRef}>Example Target</div>
//     </Draggable>
//   );
// }
//
// This can be used for arbitrarily nested components, so long as the ref ends up
// pointing to the actual child DOM node and not a custom component.
//
// For rich components, you need to both forward the ref *and props* to the underlying DOM
// element. Props must be forwarded so that DOM event handlers can be attached. 
// For example:
//
//   const Component1 = React.forwardRef(function (props, ref) {
//     return <div {...props} ref={ref}>Nested component</div>;
//   });
//
//   const nodeRef = React.useRef(null);
//   <DraggableCore onDrag={onDrag} nodeRef={nodeRef}>
//     <Component1 ref={nodeRef} />
//   </DraggableCore>
//
// Thanks to react-transition-group for the inspiration.
//
// `nodeRef` is also available on <DraggableCore>.
nodeRef: React.Ref<typeof React.Component>,

// Much like React form elements, if this property is present, the item
// becomes 'controlled' and is not responsive to user input. Use `position`
// if you need to have direct control of the element.
position: {x: number, y: number}

// A position offset to start with. Useful for giving an initial position
// to the element. Differs from `defaultPosition` in that it does not
// affect the position returned in draggable callbacks, and in that it
// accepts strings, like `{x: '10%', y: '10%'}`.
positionOffset: {x: number | string, y: number | string},

// Specifies the scale of the canvas your are dragging this element on. This allows
// you to, for example, get the correct drag deltas while you are zoomed in or out via
// a transform or matrix in the parent of this element.
scale: number
}

Note that sending className, style, or transform as properties will error - set them on the child element directly.

Controlled vs. Uncontrolled

<Draggable> is a 'batteries-included' component that manages its own state. If you want to completely control the lifecycle of the component, use <DraggableCore>.

For some users, they may want the nice state management that <Draggable> provides, but occasionally want to programmatically reposition their components. <Draggable> allows this customization via a system that is similar to how React handles form components.

If the prop position: {x: number, y: number} is defined, the <Draggable> will ignore its internal state and use the provided position instead. Alternatively, you can seed the position using defaultPosition. Technically, since <Draggable> works only on position deltas, you could also seed the initial position using CSS top/left.

We make one modification to the React philosophy here - we still allow dragging while a component is controlled. We then expect you to use at least an onDrag or onStop handler to synchronize state.

To disable dragging while controlled, send the prop disabled={true} - at this point the <Draggable> will operate like a completely static component.

<DraggableCore>

For users that require absolute control, a <DraggableCore> element is available. This is useful as an abstraction over touch and mouse events, but with full control. <DraggableCore> has no internal state.

See React-Resizable and React-Grid-Layout for some usage examples.

<DraggableCore> is a useful building block for other libraries that simply want to abstract browser-specific quirks and receive callbacks when a user attempts to move an element. It does not set styles or transforms on itself and thus must have callbacks attached to be useful.

DraggableCore API

<DraggableCore> takes a limited subset of options:

{
  allowAnyClick: boolean,
  cancel: string,
  disabled: boolean,
  enableUserSelectHack: boolean,
  offsetParent: HTMLElement,
  grid: [number, number],
  handle: string,
  onStart: DraggableEventHandler,
  onDrag: DraggableEventHandler,
  onStop: DraggableEventHandler,
  onMouseDown: (e: MouseEvent) => void,
  scale: number
}

Note that there is no start position. <DraggableCore> simply calls drag handlers with the below parameters, indicating its position (as inferred from the underlying MouseEvent) and deltas. It is up to the parent to set actual positions on <DraggableCore>.

Drag callbacks (onStart, onDrag, onStop) are called with the same arguments as <Draggable>.


Contributing

  • Fork the project
  • Run the project in development mode: $ npm run dev
  • Make changes.
  • Add appropriate tests
  • $ npm test
  • If tests don't pass, make them pass.
  • Update README with appropriate docs.
  • Commit and PR

Release checklist

  • Update CHANGELOG
  • make release-patch, make release-minor, or make-release-major
  • make publish

License

MIT