Roadmap

snapgrid sits on two framework-agnostic foundations: react-grid-layouts packing core and dnd-kits DOM engine. Today it ships as @snapgridjs/react, @snapgridjs/svelte, @snapgridjs/vue and @snapgridjs/solid, and neither the layout core nor the drag engine contains any framework code which is what makes the directions below possible.

Framework bindings

dnd-kit is framework-agnostic by design: a vanilla DOM engine with thin per-framework bindings. snapgrid is built the same way: @snapgridjs/core holds the layout math, compaction, and drag session with no framework code, and each binding is a small layer on top. Four ship today React (@snapgridjs/react), Svelte (@snapgridjs/svelte), Vue (@snapgridjs/vue) and Solid (@snapgridjs/solid) and the same core can drive more:

• Vanilla TypeScript (no framework at all).

Each binding owns only the rendering glue refs, reactivity, lifecycle while the layout behaviour stays shared, so a grid behaves identically whichever framework renders it.

Shape the roadmap

These priorities follow what people actually build with snapgrid. Have a use case, or a framework you need? Open an issue. It genuinely steers what comes next.