🚀 Path to v2.0.0 — Production-Ready Release

[jjeff]

This is the master tracking issue for shipping Resortable as a stable, production-ready 2.0.0 release. Each task below links to a discrete sub-issue.

Current snapshot (2026-06-04)

Metric	Status
Branch / version	main @ 2.0.0-alpha.1 (package.json)
Git tags	v1.0.0 (synthetic anchor for semantic-release), v2.0.0-alpha.1 (historical)
Next semantic-release version	2.0.0 (verified via --dry-run)
Lint / type-check / build	✅ passing
Unit tests	✅ 241 passing, 2 skipped
E2E tests (chromium)	✅ 154 passing, 42 skipped
Bundle (ESM gz)	21.99 kB (budget 50 kB ✅)
TypeDoc site	✅ live at https://jjeff.github.io/resortable/api/
Examples demo	✅ live at https://jjeff.github.io/resortable/demo/
LICENSE / NOTICE / SECURITY / CONTRIBUTING	✅ in place
dependency-review CI	✅ enabled
WCAG 2.1 AA axe gate	✅ chromium passes; mobile/cross-engine deferred
Published to npm	❌ — gated on user storing NPM_TOKEN + flipping npmPublish: true

Release gates

Feature parity (vs Sortable.js v1.x)

• Parity: Implement HTML5 fallback drag system #29 — HTML5 fallback drag system (forceFallback, fallbackClass, fallbackOnBody, fallbackTolerance, fallbackOffset) — PRs feat: wire forceFallback + fallbackClass into pointer drag pipeline (#29) #53, feat: wire fallbackOnBody + fallbackOffset into ghost positioning (#29) #54, feat: wire fallbackTolerance pre-commit threshold (#29) #55, feat: complete HTML5 fallback drag system (#29 — final) #56
• Parity: Add 'ignore' option (legacy default 'a, img') #30 — ignore option (legacy default 'a, img') — PR feat: add 'ignore' option for click-through on links/images (#30) #82
• Parity: Wire up declared-but-unused options (dragoverBubble, removeCloneOnHide, emptyInsertThreshold, dropBubble) #31 — Wire declared-but-unused options (dragoverBubble, removeCloneOnHide, emptyInsertThreshold, dropBubble) — PR fix: recognize empty containers as drop targets in pointer drag (#32) #50
• Bug: Empty containers not recognized as drop zones #32 — Bug: empty containers not recognized as drop zones — PR ci: enforce bundle-size budget via size-limit (#39) #49
• Wire onMove(event, originalEvent) with native event object #33 — Wire onMove(event, originalEvent) with native event — PRs feat: wire onMove with native event + cancellation (#33) #59, feat: extend onMove to cross-zone branches (#60) #61
• Reconcile core multi-drag with MultiDragPlugin #34 — Reconcile core multi-drag with MultiDragPlugin — PR refactor: reconcile multi-drag — keep as core, remove MultiDragPlugin shim (#34) #91 (BREAKING: shim removed; use core multiDrag: true)
• Bug: Single-select mode doesn't deselect prior item when Space-selecting another #46 — Single-select mode deselect bug — PR fix: deselect prior item in single-select mode (#46) #58

Quality & test coverage

• Tests: Un-skip and stabilize the deferred E2E specs #35 — Un-skip and stabilize the deferred E2E specs — PR test: triage E2E skips + un-skip easy wins (#35) #80 (triage pass: 65 audited, 3 un-skipped, 7 sub-issues filed Test: Atomic page.dragAndDrop swallows onSort/onChange/onMove intermediate events #73-79, 22 valid conditionals confirmed)
• Tests: Implement Shift+Arrow selection extension (skipped unit tests) #36 — Implement Shift+Arrow selection extension
• CI: Re-enable Playwright E2E on GitHub-hosted Linux runner #37 — Re-enable Playwright E2E on GitHub-hosted Linux runner — PR ci: re-enable Playwright e2e on GitHub-hosted Linux (chromium-only) #45
• Tests: Cross-browser Playwright matrix (Chromium / Firefox / WebKit) #38 — Cross-browser Playwright matrix (Firefox/WebKit on Linux)
• Performance: Benchmark suite + 60fps assertion + bundle-size CI gate #39 — Performance benchmark suite + 60fps assertion + bundle-size CI gate (bundle-size portion) — PR fix: recognize empty containers as drop targets in pointer drag (#32) #50
• Flake: waitForAnimations helper AbortError during teardown #47 — waitForAnimations AbortError flake — fix shipped in helpers; soak validated by 30+ subsequent clean PRs
• Bug: Three e2e tests fail in [Mobile Chrome] viewport (Pixel 5 emulation) #48 — Three Mobile Chrome (Pixel 5) tests failing — PR test: un-skip Mobile Chrome e2e tests, make assertion device-aware (#48) #83 (device-aware assertion via runtime navigator.maxTouchPoints check)
• Flaky: Mobile Safari ghost-elements:153 cross-list drag #62 — Mobile Safari ghost-elements:153 cross-list drag flake — PR test: skip Mobile Safari dragAndDrop flakes (#62) #81 (project-scoped skip)
• Test: Atomic page.dragAndDrop swallows onSort/onChange/onMove intermediate events #73 — Atomic dragAndDrop swallows onSort/onChange/onMove intermediate events
• Test: basic-sortable touch input + hover effects are non-deterministic #74 — basic-sortable touch input + hover effects non-deterministic
• Test: feature-demos nested-list and clone-mode scenarios skipped #75 — feature-demos nested-list + clone-mode regressions
• Test: delay-options E2E specs blocked on timing simulation #76 — delay-options E2E timing simulation
• Test: swapThreshold/invertSwap/direction suite skipped (CSS-positioned fixture needed) #77 — swap-behavior CSS-positioned fixture needed
• Test: cross-list keyboard drag-and-drop not implemented #78 — Cross-list keyboard drag-and-drop
• Test: animation.spec.ts integration suite skipped (needs full pipeline rework) #79 — animation.spec.ts integration suite rework

Accessibility

• A11y: Formal WCAG 2.1 AA audit + automated axe checks in CI #40 — Formal WCAG 2.1 AA audit + automated axe checks in CI — PR test: add WCAG 2.1 AA axe-core checks + a11y documentation (#40) #92 (10/10 pages pass on chromium; mobile a11y deferred to separate suite when added)

Documentation

• Documentation: API reference, migration guide, examples, plugin guide #41 — API reference, migration guide, examples, plugin guide — PRs docs: migration guide from Sortable.js v1 (#66) #67, docs: curated examples site (#65) #68, docs: README rewrite + CDN snippets (#64) #69, docs: lift plugin guide + fix TypeDoc warnings + docs landing (#63) #70, feat: bundle examples + demo as gh-pages live site (#71) #72 (all 5 sub-issues delivered; gh-pages live)

Release engineering

• Release engineering: npm publish, provenance, CDN, dry-run, security #42 — npm publish, provenance, CDN, dry-run, security — partially complete:
  • LICENSE + NOTICE files (chore: release engineering prep — license, NOTICE, dependency-review, dry-run validation (#42) #84)
  • dependency-review CI workflow (chore: release engineering prep — license, NOTICE, dependency-review, dry-run validation (#42) #84)
  • semantic-release dry-run validated (computes 2.0.0 next)
  • SECURITY.md + CONTRIBUTING.md (chore: fix dist ESM filename + add SECURITY.md / CONTRIBUTING.md #90)
  • dist filename matches package.json exports (sortable.esm.js) (chore: fix dist ESM filename + add SECURITY.md / CONTRIBUTING.md #90)
  • User TODO: Store NPM_TOKEN secret (Settings → Secrets and variables → Actions)
  • User TODO: Flip npmPublish: false → true in .releaserc.json
  • First publish triggers automatically on next push to main after the flip
  • Verify UMD reachable via unpkg + jsDelivr post-publish
  • Cut beta → RC → 2.0.0 stable cycle from develop branch (per .releaserc.json branch config)
• Hygiene: Pre-release cleanup (TODOs, stubs, types, Sortable.utils parity) #43 — Pre-release cleanup (TODOs, stubs, public types, Sortable.utils parity) — PR chore: pre-release cleanup — TODOs, stubs, Sortable.utils parity (#43) #93 (0 TODOs in src/, +4 utils: off/closest/toggleClass/clone, +16 tests, 2 dead types removed)

Out of scope for 2.0.0

Framework wrappers (React / Vue / Angular) ship as separate packages post-2.0.

How to use this issue

• An item is "done" when its sub-issue is closed.
• Release blockers carry the release-blocker label; downgrade requires maintainer approval.
• Beta cut (Release engineering: npm publish, provenance, CDN, dry-run, security #42) requires all release-blockers closed → currently all closed except #42 (user action) and the seven #73-79 follow-ups (deferred).