Update dependency react-draggable to v4 #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.2.1
->^4.0.0
Release Notes
react-grid-layout/react-draggable (react-draggable)
v4.4.6
Compare Source
v4.4.5
Compare Source
grid
prop unused inhandleDragStop
#621children
prop missing in TypeScript definition #648v4.4.4
Compare Source
documentElement.style
actually exists. Fixes crashes in some obscure environments. #574 #575peerDependencies
again to fix Yarn PnPclassnames
withclsx
to save a few bytesref
functionality and additional README content onnodeRef
v4.4.3
Compare Source
nodeRef
to TypeScript definitionsv4.4.2
Compare Source
v4.4.1
Compare Source
here as they won't be significantly tree-shook, and it bloats
the published package.
selecting "module" because "browser" is no longer present.
v4.4.0
Compare Source
nodeRef
:Unfortunately, in order for
<Draggable>
to work properly, we need raw accessto the underlying DOM node. If you want to avoid the warning, pass a
nodeRef
as in this example:
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>
.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
bundler configurations.
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.
The browser build will likely be removed entirely in 5.0.
bounds
optional in TypeScript #473v4.3.1
Compare Source
<DraggableCore>
not to pass styles.React.cloneElement
has an odd quirk. When you do:style
ends up undefined.babel-loader
cache does not invalidate when it should. I had modified webpack.config.js in the last version but it reused stale cache.v4.3.0
Compare Source
<Draggable>
.<Draggable>
were not scrollable on touch devices due to the outer container havingtouch-action: none
.e.preventDefault()
. However, due to changes in Chrome >= 56, this is only possible onnon-passive event handlers. To fix this, we now add/remove the touchEvent on lifecycle events rather than using React's event system.
v4.2.0
Compare Source
scale
parameter also while dragging an element. #438process.env.DRAGGABLE_DEBUG
checks in cjs/esm. #445v4.1.0
Compare Source
Add
"module"
topackage.json
. There are now three builds:"main"
: ES5-compatible CJS build, suitable for most use cases with maximum compatibility."web"
: Minified UMD bundle exporting towindow.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.
No compatibility changes are expected.
v4.0.3
Compare Source
v4.0.2
Compare Source
v4.0.1
Compare Source
v3.3.2
Compare Source
all: inherit
instead ofbackground: transparent;
to fix selection styles.v3.3.1
Compare Source
componentWillMount
deprecation.v3.3.0
Compare Source
positionOffset
prop, which can be Numbers (px) or string percentages (like"10%"
). See the README for more.Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.