feat(ux): scroll while dragging

[itsjavi]

I've seen that there is a scroller plugin in the codebase (which apparently is not bundled in the dist files) and I've tried to copy-paste it and use it but it doesn't work.

There's another problem (Idk. if it's related) on touch screens, which makes the droppables disable the device 'drag to scroll' behavior. If you try my example on mobile you can't scroll when touching the empty cells (which are only droppables). Non-empty cells (that have a pokemon) are both draggable and droppable.

Is there any plans to improve this behaviour of the library? As you can see in the video, the page doesn't scroll down when the draggable is in the viewport boundaries.

I can try to help with a PR if you let me know what would be the necessary changes.

Screen.Recording.2025-04-24.at.01.19.01.mov

[zheksoon]

Hi! I have one old example with the scroller plugin, I will try to reconstruct it soon. Thanks for the attention!

[zheksoon]

Finally, check out this sandbox for the scroller example:
https://codesandbox.io/p/sandbox/snapdrag-squares-rb7kp8

The scroller plugin from the main branch is a bit invalid, you can create a PR with the updated scroller from the sandbox (I can't commit at the moment). If you do so, create a separate directory plugins as a separate module (like core inside the main directory), and put the plugin there (so it can be imported from snapdrag/plugins). And you can fix the React 19 incompatibility as well. Thanks!

[itsjavi]

@zheksoon thanks for the guidance. I had many problems setting up the local dev environment. What is your workflow? Having deps as `file:.." makes it hard to debug it locally with the examples app.

I had to do all of this in order to initialize the project:

yarn install
cd core && yarn install && cd -
cd react && yarn install && cd -
yarn build &&
cd examples && yarn install

Would you be open for me to switch the project to use yarn workspaces and put the packages in a packages dir? I can do it in a separate PR.

[zheksoon]

Cool, glad it works for you! About Yarn workspaces, yes, I think it's a good idea, as the library is mainly for React at the moment (core is not documented, and the config format is somehow different). So yeah, making it with workspaces totally makes sense. The only thing - plug-ins should be not embedded into the main package and done as a separate sub-package (as the core done at the moment). Thanks for your contribution, it's very valuable!