strml

mzabriskie

react-draggable

Error

Ignore

Warn

License

Maintenance

Miscellaneous

Quality

Supply chain risk

Vulnerability

Admins only

Organization members

Dashboard

<upgradeLink>Upgrade</upgradeLink> to access this feature

About

Blog

Socket CLI

Customers

Socket Dependency Search

Docs

Socket for GitHub

Love

Impersonation Mode Active

Update your browser to the latest version for the best experience.

Your web browser is outdated

Use another browser for the best experience.

Your web browser is unsupported

{{count, number}} commits last two months

{{count, number}} critical severity alert

{{count, number}} critical severity alerts

{{count, number}} dependency vulnerability

{{count, number}} dependency vulnerabilities

{{count, number}} development dependencies

{{count, number}} transitive dependencies

{{count, number}} version published last month

{{count, number}} versions published last month

{{count, number}} version published in last two months

{{count, number}} versions published in last two months

{{count, number}} version published last week

{{count, number}} versions published last week

{{count, number}} version published last year

{{count, number}} versions published last year

Socket undergoes annual SOC2 Type II audits. Socket customers can request a copy of the full SOC2 Type II report.

Allows organization owners and admins to access detailed records of actions taken by members of their organization, complete with timestamps.

Prevent compromised packages from infiltrating your supply chain by monitoring for changes in real-time.

Join our Discord community to get help from Socket engineers and other Socket users.

Compare millions of open source packages on socket.dev

Detect malicious code and risky behavior (e.g. network) in your dependencies using "deep package inspection"

All data is encrypted in transit and at rest using industry standard encryption algorithms.

Get a dedicated Socket account manager and access to Socket’s Customer Success team.

Get dedicated support from Socket engineers via email and Slack.

"Shift left" with the Socket Chrome extension and give intervene early, before developers choose risky or low quality dependencies.

Catch developers using risky dependencies and give them a "speed bump" to encourage good behavior

Install the Socket GitHub app to receive real-time dependency scanning and reports with every pull request.

Integrate Socket into your GitHub SCM to prevent risky dependencies from being installed.

Socket scans for vulnerabilities in your dependencies, including CVEs, security advisories, and more.

Socket supports dependencies in many languages, with most popular ecosystems coming in 2024. We've got you covered no matter what languages you use.

Enforce license policies across your organization

Receive a Microsoft Teams message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Get help migrating from Socket's free plan to Socket's paid plans.

Run Socket on-premises or in your own cloud environment.

Query for any dependency (at any version) across your entire organization

Integrate Socket into your CI/CD pipeline to prevent risky dependencies from being deployed to production.

Analyze an entire project to find supply chain risks

Tag projects to organize and filter your projects

Restrict access based on the roles of individual users within an organization.

Receive a Slack message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket is SOC2 Type II compliant and undergoes annual audits.

The Socket CLI allows teams to prevent risky dependencies from being installed, and to get dependency insights from the command line.

Socket supports SAML SSO for single sign-on and identity management.

Integrate Socket into your VS Code IDE to prevent risky dependencies from being installed.

Get a POST request anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket will analyzed your SBOMs up to a maximum number of dependencies.

API that allows you to analyze a project, lookup package scores and alerts, and more.

Create API tokens to authenticate with the Socket API and CLI.

The number of developers in your team. A developer is someone who made a commit to your organization's repositories scanned by Socket in the past month.

Use Socket to protect your private repositories.

Socket is always free for open source projects.

Socket retains all reporting data for 3 months, 1 year, or a custom term of your choice.

Access the threat feed that powers Socket.

Unlimited scale, self-hosting, and priority support for large teams.

For open-source projects, individuals, and small teams.

For growing teams with enhanced scale, security, and support.

There is a package with a similar name that is downloaded much more often.

There are packages with similar names that are downloaded much more often.

This may not be the package you want!

Instance

Alert Locations

Package

The {{ecosystem}} package {{- packageName}} receives a total of <strong>{{numWeeklyDownloadCount, number}}</strong> weekly downloads. As such, {{- packageName}} popularity was classified as <strong>{{popularity}}</strong>.

Is {{- packageName}} popular?

Is {{- packageName}} safe to use?

Is {{- packageName}} well maintained?

What is {{- packageName}}?

{{packageDescription}}Version: {{versionString}} was published by {{publisherName}}. Start using Socket to analyze {{- packageName}} and its {{dependencyCount, number}} dependencies to secure your app from supply chain attacks.

Sorry, it seems this package was removed from the registry

Package was removed

This package version has been unpublished, mostly likely due to security reasons

Package version was removed

Provide a detailed description of the malware...

Socket fights vulnerabilities and provides visibility, defense-in-depth, and proactive supply chain protection for JavaScript, Python, and Go dependencies.

Socket - Secure your dependencies. Ship with confidence.

Compare versions

{{- packageName}} - npm Package Compare versions

- Fix: Remove "module" definition in package.json

  - Giving up on this: there isn't a great reason to publish modules

    here as they won't be significantly tree-shook, and it bloats

  - Fixes incompatiblity in 4.4.0 with webpack, where webpack is now

    selecting "module" because "browser" is no longer present.

  - 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`

      const nodeRef = React.useRef(null);

          <div ref={nodeRef}>Example Target</div>

    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.

    Thanks to react-transition-group for the inspiration.

    `nodeRef` is also available on <DraggableCore>.

- Remove "browser" field in "package.json":

  - There is nothing special in the browser build that is actually practical

    for modern use. The "browser" field, as defined in 

    https://github.com/defunctzombie/package-browser-field-spec#overview,

    indicates that you should use it if you are directly accessing globals,

    using browser-specific features, dom manipulation, etc.

    React components like react-draggable are built to do minimal raw

    DOM manipulation, and to always gate this behind conditionals to ensure

    that server-side rendering still works. We don't make any changes

    to any of that for the "browser" build, so it's entirely redundant.

    This should also fix the "Super expression must either be null or

    a function" error (#472) that some users have experienced with particular

    The browser build may still be imported at "build/web/react-draggable.min.js".

    This is to prevent breakage only. The file is no longer minified to prevent

    possible [terser bugs](https://github.com/terser/terser/issues/308).

  - The browser build will likely be removed entirely in 5.0.

- Fix: Make `bounds` optional in TypeScript [#473](https://github.com/strml/react-draggable/pull/473)

- Fixed a serious bug that caused `<DraggableCore>` not to pass styles.

  - `React.cloneElement` has an odd quirk. When you do:

    return React.cloneElement(this.props.children, {style: this.props.children.props.style});

- Fixed a bug that caused debug output to show up in the build. 

  - `babel-loader` cache does not invalidate when it should. I had modified webpack.config.js in the last version but it reused stale cache.

- Fix setState warning after dismount if drag still active. Harmless, but prints a warning. [#424](https://github.com/mzabriskie/react-draggable/pull/424)

- Fix a long-standing issue where text inputs would unfocus upon dismounting a `<Draggable>`.

  - Thanks @schnerd, [#450](https://github.com/mzabriskie/react-draggable/pull/450)

- Fix an issue where the insides of a `<Draggable>` were not scrollable on touch devices due to the outer container having `touch-action: none`.

    - This was a long-standing hack for mobile devices. Without it, the page will scroll while you drag the element.

    - The new solution will simply cancel the touch event `e.preventDefault()`. However, due to changes in Chrome >= 56, this is only possible on 

      non-passive event handlers. To fix this, we now add/remove the touchEvent on lifecycle events rather than using React's event system.

    - [#465](https://github.com/mzabriskie/react-draggable/pull/465)

- Upgrade devDeps and fix security warnings. None of them actually applied to this module.

- Fix: Apply `scale` parameter also while dragging an element. [#438](https://github.com/mzabriskie/react-draggable/pull/438)

- Fix: Don't ship `process.env.DRAGGABLE_DEBUG` checks in cjs/esm. [#445](https://github.com/mzabriskie/react-draggable/pull/445)

- Add `"module"` to `package.json`. There are now three builds:

  * **`"main"`**: ES5-compatible CJS build, suitable for most use cases with maximum compatibility.

    - For legacy reasons, this has exports of the following shape, which ensures no surprises in CJS or ESM polyfilled environments:

      module.exports.default = Draggable;

      module.exports.DraggableCore = DraggableCore;

  * **`"web"`**: Minified UMD bundle exporting to `window.ReactDraggable` with the same ES compatibility as the "main" build.

  * **`"module"`**: ES6-compatible build using import/export.

  This should fix issues like https://github.com/STRML/react-resizable/issues/113 while allowing modern bundlers to consume esm modules in the future.

- Add typings and sourcemap to published npm package.

  - This compresses well so it does not bloat the package by much. Would be nice if npm had another delivery mechanism for optional modes, like web/TS.

- Republish to fix packaging errors. Fixes #426

  "description": "React draggable component",

    "test-debug": "karma start --browsers=Chrome --single-run=false --auto-watch=true",

    "test-firefox": "karma start --browsers=Firefox --single-run=false --auto-watch=true",

    "test-ie": "karma start --browsers=IE --single-run=false --auto-watch=true",

    "url": "https://github.com/mzabriskie/react-draggable.git"

    "url": "https://github.com/mzabriskie/react-draggable/issues"

  "homepage": "https://github.com/mzabriskie/react-draggable",

    "@babel/plugin-proposal-class-properties": "^7.8.3",

    "@babel/plugin-transform-flow-comments": "^7.8.3",

    "babel-plugin-transform-inline-environment-variables": "^0.4.3",

    "karma-phantomjs-launcher": "^1.0.4",

		{
		"name": "react-draggable",
		"version": "4.4.0",
		"version": "4.4.1",
		"description": "React draggable component",
		@@ -59,3 +59,3 @@ "main": "build/cjs/cjs.js",
		"jasmine-core": "^3.5.0",
		"karma": "^5.0.2",
		"karma": "^4.4.1",
		"karma-chrome-launcher": "^3.1.0",
		@@ -62,0 +62,0 @@ "karma-cli": "2.0.0",

Fixed alerts

Improved metrics

Worsened metrics

		# Changelog

		### 4.4.1 (May 12, 2020)

		- Fix: Remove "module" definition in package.json
		- Giving up on this: there isn't a great reason to publish modules
		here as they won't be significantly tree-shook, and it bloats
		the published package.
		- Fixes incompatiblity in 4.4.0 with webpack, where webpack is now
		selecting "module" because "browser" is no longer present.

		### 4.4.0 (May 12, 2020)
		@@ -4,0 +13,0 @@