sortablejs VS React

We can also pass all the options for SortableJS as the second parameter. See SortableJS Docs.

SortableJS is a touch-friendly library that enables drag-and-drop sorting of lists. Its simple API and flexibility make it a go-to solution for implementing sortable lists, providing an intuitive user experience for rearranging items on the fly.

Sortable.js

We've been using SortableJS for years for similar functionality.

https://sortablejs.github.io/Sortable/

Well, it worked. But only for one case: dragging stuff within only one column. You see, stimulus-sortable uses SortableJS under the hood, which is powerful.

Maybe: https://github.com/SortableJS/Sortable Can do this not sure.

Well, there are obvious leading contenders like `https://sortablejs.github.io/Sortable/` and, within the `vue` space, `https://sortablejs.github.io/vue.draggable.next/`. Most of the stuff I looked at was unmaintained (lots not updated for vue3).

I really disliked the vuedraggable was handling nesting, and it's just a wrapper around a sortable. At the end of the day, my problem was simple enough that I didn't want a 500kb dependency. If you're wanting to do something like the OP but with nesting, I'd definitely start by looking at Sortable, though (maybe wrapping it the way you want).

Have you looked into alternatives to SortableJS btw? It's a good library but it's also pretty big (43kb) based on https://github.com/SortableJS/Sortable/blob/master/Sortable.min.js.

Official React Documentation: react.dev MDN Javascript Documentation: developer.mozilla.org/JavaScript

Early in my career, I struggled to understand how React’s state updates actually worked. Docs gave me the basics, but edge cases around batching were confusing. One weekend, I pulled up the React source code on GitHub and traced how state changes bubbled through the scheduler. Suddenly, the “weird bugs” I hit at work made sense because I wasn’t guessing anymore, I’d seen the engine.

3. Next.js and React (Frontend framework)

My primary passion is backend development, but I wanted to build a user-friendly frontend to complete this project. Given my experience with React, Next.js was the obvious choice due to its excellent documentation and ease of use.

Check out the React 19 Upgrade Guide for more details. Have fun coding, and share in the comments what you’re building with React 19! 🎉

React Official Documentation — Start here for official guides and tutorials

At IVAO, we partially follow micro-services best practices. This means each business group (e.g., Flight tracking, Flight planning, Air Traffic controlling, Training) has its own NestJS API and ReactJS frontend. But we took a shortcut on the DB side, as we have quite some references across systems, especially for user IDs, airports, etc... We decided to have a single MariaDB instance while having a dedicated logical database for each API, so we still have a separation of concerns but we can guarantee data integrity with foreign keys across those databases.

React.js (fast, large ecosystem)

Tools: V0 by Vercel, shadcn/ui, React, Tailwind CSS V0 turns natural language prompts into ready-to-use React + Tailwind UI code. Ask for “a responsive SaaS dashboard with a dark theme and collapsible sidebar” and you get production-ready code instantly, accessible, tweakable, and not locked into rigid templates.