comparekloq vs Schedule-Xchecked 2026-09-01
Schedule-X keeps dragging in premium plugins. In kloq every interaction ships in the npm package.
Schedule-X is a good-looking, modern calendar with an MIT core and optional premium plugins. This comparison looks at which interactions each project includes in its npm package.
- @schedule-x/calendar
- v4.7.0
- npm, last week
- 174,285
- rows kloq wins
- 6
- rows kloq loses
- 1
01side by side
The table, with the losses left in.
Every number below was read from npm on 2026-09-01. Sources are at the foot of the page — check them.
| Compared | kloq | Schedule-X | verdict |
|---|---|---|---|
| Core licence | MIT | MIT | even |
| Drag and drop | In the npm build | Premium plugin | kloq |
| Resize | In the npm build | Premium plugin | kloq |
| Drag to create | In the npm build | Premium plugin | kloq |
| Event modal / panel | In the npm build | Premium plugin | kloq |
| Resource schedulerBoth schedule resources on a horizontal axis. kloq's ships in the component; Schedule-X's resource view is behind the premium licence. | Built in | Premium plugin | kloq |
| RuntimeSchedule-X ships a React wrapper over a Preact core. | React 19 | Preact with signals, plus a Temporal polyfill | even |
| Do you get the source? | Yes — the whole library lands in your repo | Premium plugins are served from a private npm registry | kloq |
| Maturity | 0.1.0, new | 4.7.0, ~174k npm downloads a week | them |
02choose schedule-x
When Schedule-X is the right answer.
Four cases where we would tell you to install theirs. If one of them is your case, stop reading — you have your answer and it isn't us.
You want a more established resource scheduler
kloq's resource timeline is new in 0.1.0, with no production miles on it yet. Schedule-X's predates it and has a longer release history.
You want a Temporal-based date model
Schedule-X builds on the Temporal API through a polyfill it declares as a peer dependency. kloq works in Date and Intl, which is more familiar and less future-proof.
You are not on React
The Preact core means Schedule-X runs in more places than a React-only component does.
You want a project that has shipped four majors
Schedule-X is at 4.7.0 with a real release history. kloq is at 0.1.0 and has not earned that comparison.
03choose kloq
And when we would say ours.
The narrower case — but it is the one this whole library was built for.
You do not want the interactions behind a paywall
Drag, resize, drag-to-create and the event panel are premium plugins in Schedule-X. In kloq they are in the npm build, including the design mode.
You want the source in your own repo
The shadcn registry installs kloq as files under components/kloq/, where you can adjust its internals directly.
You want one React component
kloq's views and interactions share one component API. Schedule-X composes its premium interactions from plugins around a Preact core.
You are already a React and Tailwind shop
kloq is a React 19 component styled with Tailwind v4 tokens, scoped so it never writes to :root, html or body. No Preact layer in between.
04migration
What moving off Schedule-X looks like.
Not a codemod — an honest sketch of which concept becomes which. Most of the work is deleting things.
createCalendar({ views, events })becomes<Kloq defaultEvents={events} view="week" />A React component with props rather than a calendar instance you construct and hand to a wrapper.
createDragAndDropPlugin() (premium)becomes— nothing —There is no plugin to install.
callbacks.onEventUpdatebecomesonCommit(change)Same idea. kloq applies optimistically and springs the block back if you reject it.
$app.calendarEvents.set(...)becomesevents / onEventsChangeControlled React state instead of signals you write into.
05check us
Where these numbers came from.
Read on 2026-09-01. If something below has moved, the table is wrong and we would like to know.