Bump react-draggable from 2.2.6 to 4.4.3

Bumps react-draggable from 2.2.6 to 4.4.3.

Changelog

Sourced from react-draggable's changelog.

4.4.3 (June 8, 2020)

Add nodeRef to TypeScript definitions

4.4.2 (May 14, 2020)

Fix: Remove "module" from package.json (it is no longer being built)

Fixes #482

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)
Add nodeRef:
If running in React Strict mode, ReactDOM.findDOMNode() is deprecated. Unfortunately, in order for 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. Thanks to react-transition-group for the inspiration. nodeRef is also available on .
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.

Commits

9c5e8c3 release v4.4.3
6de32a1 feat(typescript): add nodeRef to TS definitions (#494)
13c96c8 build(deps): bump websocket-extensions from 0.1.3 to 0.1.4 (#493)
a26ed8d chore(deps): update devDeps, rem Node 8 from Travis (#490)
2c15caf release v4.4.2
300f107 fix(module): rem "module" from package.json
c7d87c3 release v4.4.1
fa030e2 fix(build): no longer publishing "module" either
75d75d7 fix(test): downgrade karma so we can keep testing Node 8
002671f release v4.4.0
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

MemeLabs / Rustla2

Bump react-draggable from 2.2.6 to 4.4.3 #317

4.4.3 (June 8, 2020)

4.4.2 (May 14, 2020)

4.4.1 (May 12, 2020)

4.4.0 (May 12, 2020)