Back to Blog
Close up of computer screen with code displayed
Comparison
8 min read

Svelte Scheduler Components in 2026: Options Compared

By SimpleCalendarJS Team

SimpleCalendarJS~14 KB gzipped · Zero dependencies · Any framework
Short answer

For a Svelte scheduler, use EventCalendar (@event-calendar/core, MIT) if you need free resource and timeline views, SVAR Svelte Calendar if you want a native Svelte 5 component with a built-in editor, or a lightweight framework-agnostic calendar like SimpleCalendarJS mounted with a Svelte action for month, week, day and list views.

If you need a Svelte scheduler (a week or day grid with timed events you can drag, plus a month overview), you'll find a handful of real choices and plenty of abandoned Svelte 3 packages. This post compares the options still worth considering in 2026, the native Svelte 5 components and the framework-agnostic libraries you mount yourself, then builds a working scheduler with a Svelte action.

If you only need a basic calendar on a page, start with How to Add a Calendar to a Svelte App. This post is about choosing a scheduler: something with time grids, drag and drop, and events loaded from your backend.

What a Svelte Scheduler Needs to Do

Before you compare libraries, decide which of these you actually need. Most of the price and size differences come from the last three rows.

  • Time-grid views: week and day views with hour slots, plus a month view for an overview.
  • Loading by date range: fetch only the events for the visible week or month from your API.
  • Drag and drop and resize: move a booking to another slot, or stretch it to change its length.
  • Click to create: click an empty slot to open your own form.
  • Resource or timeline views: rows per person, room or machine. This is where most libraries start charging.
  • Recurring events: RRULE-style series that can be edited as a whole or one occurrence at a time.
  • Time zones: showing events in a zone other than the browser's.

A clinic booking page or a team's week planner usually needs the first four. A rota across 30 staff needs resource rows. The general trade-offs are covered in JavaScript Calendar Scheduler: Choosing and Building One; this post focuses on what works well in Svelte.

Svelte Scheduler Options Compared

All facts below are from each project's own docs or repository, as of November 2026.

LibrarySvelte integrationLicenseResource / timeline viewsDrag & drop
EventCalendar (@event-calendar/core)Native Svelte 5 componentMITYes, free pluginsYes, Interaction plugin
SVAR Svelte Calendar (@svar-ui/svelte-calendar)Native Svelte 5 componentMIT core + paid PROPRO onlyYes, in the free core
Schedule-X (@schedule-x/svelte)Svelte wrapper componentFree core + paid PremiumPremiumPremium since v4
DHTMLX SchedulerHand-written component (no wrapper)Commercial (trial package available)See DHTMLX editionsYes
SimpleCalendarJS (simple-calendar-js)Core class in a Svelte actionFree for personal, educational and open source use; commercial license requiredNoYes, move and resize

One package you'll often see in search results, beyonk-group/svelte-scheduler, targets Svelte 3 and its README says: "This project is a work-in-progress. It doesn't work as advertised right now." Leave it out of new projects.

Need a calendar in your app?

SimpleCalendarJS: ~14 KB gzipped, zero dependencies, works in any framework. Free for personal use.

The Libraries in Detail

EventCalendar (vkurko/calendar)

EventCalendar is the strongest free option if you need scheduler-style views. Its README describes it as a full-sized drag & drop event calendar with resource and timeline views, MIT-licensed, and "Lightweight (39kb br compressed)" for the zero-dependency standalone bundle. The latest release when this was written was v5.21.0 (November 2026), so the project is actively maintained.

Features ship as plugins: DayGrid, TimeGrid, List, ResourceTimeGrid, ResourceTimeline and Interaction (drag and drop). In Svelte 5 it's a real component, and options live in $state:

<script> import { Calendar, TimeGrid } from '@event-calendar/core'; let options = $state({ view: 'timeGridWeek', events: [] }); </script> <Calendar plugins={[TimeGrid]} {options} />

Choose it when you need resource columns or a timeline for free and you're comfortable with a FullCalendar-like option model. It's also usable outside Svelte through EventCalendar.create(element, options).

SVAR Svelte Calendar

SVAR's calendar is a native Svelte 5 component with TypeScript support. The MIT core includes day, week and month views, drag and drop, drag-to-create, a built-in event editor, a context menu, calendar groups, filtering and iCal import/export, according to SVAR's release post. The paid PRO edition adds agenda, year, resource and timeline views, editable recurring events, time zone switching, export to PDF/PNG/Excel, and, per the product page, dynamic loading of events by date range.

That last point matters: if your backend has years of bookings, check whether the free core's loading model fits before you commit.

Choose it when you want a complete scheduling UI (editor included) with idiomatic Svelte props and are willing to buy PRO if you later need resources or recurrence.

Schedule-X

Schedule-X has an official Svelte package. The ScheduleXCalendar component receives a calendar app created with createCalendar(). Installation pulls in a few extras: the docs list @schedule-x/svelte, @schedule-x/calendar, @schedule-x/theme-default and temporal-polyfill, plus preact and @preact/signals as peer dependencies. Events use the Temporal API (Temporal.PlainDate, Temporal.ZonedDateTime).

The important licensing change came in v4: @schedule-x/drag-and-drop and @schedule-x/resize became @sx-premium/drag-and-drop and @sx-premium/resize, and the new resource view shipped as Premium. The maintainer describes the split as free for displaying scheduling info and Premium for interacting with and modifying it.

Choose it when you want a modern, Temporal-based display calendar, or you're happy to pay for Premium interaction features.

DHTMLX Scheduler

DHTMLX Scheduler is a mature commercial scheduler. It has no Svelte wrapper: the official guide builds a Svelte component by hand that calls Scheduler.getSchedulerInstance() and init() in onMount, and calls scheduler.destructor() in the cleanup. The tutorial installs the evaluation package @dhx/trial-scheduler, and PRO builds come from a private npm repository. The guide's sample code uses Svelte 3/4 syntax (export let, $:), which still runs in Svelte 5 but isn't runes-style.

Choose it when you need an enterprise feature set and support contract, and a commercial license is already in the budget.

Building a Svelte Scheduler With SimpleCalendarJS

SimpleCalendarJS fits a narrower case: you need month, week, day and list views, drag to move and resize, and click-to-create, in about 14 KB gzipped JS (~19 KB with CSS) and zero dependencies. It's a plain JavaScript class, so in Svelte you mount it with an action. Svelte runs the action only in the browser when the element mounts, and the $effect teardown destroys the instance when it unmounts.

Install it:

npm install simple-calendar-js

Here's a complete week-view scheduler component. It keeps bookings in a local array so you can paste and run it, and shows where your API calls go.

<script> import SimpleCalendarJs from 'simple-calendar-js'; import 'simple-calendar-js/dist/simple-calendar-js.min.css'; let calendar = null; // Replace with data from your API (see fetchEvents below). let bookings = [ { id: 1, title: 'Design review', start: new Date(2026, 10, 23, 10, 0), end: new Date(2026, 10, 23, 11, 30), color: '#4f46e5', description: 'Room 2, bring the prototype' }, { id: 2, title: 'Client call', start: new Date(2026, 10, 24, 14, 0), end: new Date(2026, 10, 24, 15, 0), color: '#0891b2' }, { id: 3, title: 'Offsite', start: new Date(2026, 10, 26), end: new Date(2026, 10, 26), allDay: true, color: '#16a34a' } ]; let nextId = 4; function scheduler(node) { calendar = new SimpleCalendarJs(node, { defaultView: 'week', enabledViews: ['month', 'week', 'day', 'list'], defaultDate: new Date(2026, 10, 23), weekStartsOn: 1, use24Hour: true, enableDragDrop: true, enableResize: true, autoContrastText: true, // Called with the visible range; results are cached per month grid. fetchEvents: async (start, end) => { // With a backend: // const res = await fetch(`/api/bookings?start=${start.toISOString()}&end=${end.toISOString()}`); // return res.json(); return bookings.filter((b) => b.start < end && b.end >= start); }, // Click an empty slot to create a booking (swap prompt for your own form). onSlotClick: (date) => { const title = prompt('Booking title?'); if (!title) return; const end = new Date(date.getTime() + 60 * 60 * 1000); bookings = [...bookings, { id: nextId++, title, start: date, end }]; calendar.refresh(); }, // Fires after a drag or a resize. onEventDrop: async (event, oldStart, oldEnd, newStart, newEnd) => { bookings = bookings.map((b) => b.id === event.id ? { ...b, start: newStart, end: newEnd } : b ); // With a backend, persist and roll back on failure: // const res = await fetch(`/api/bookings/${event.id}`, { // method: 'PATCH', // headers: { 'Content-Type': 'application/json' }, // body: JSON.stringify({ start: newStart, end: newEnd }) // }); // if (!res.ok) { /* restore oldStart/oldEnd in your data */ } calendar.refresh(); }, onEventClick: (event) => { alert(`${event.title}\n${event.start.toLocaleString()}`); } }); $effect(() => { return () => { calendar?.destroy(); calendar = null; }; }); } </script> <div use:scheduler style="height: 700px"></div>

A few details that matter:

  1. The inline style="height: 700px" gives a fixed-height layout, so month view shows "+N more" instead of growing. A height from a stylesheet or a utility class doesn't count; it has to be inline.
  2. Events always come from fetchEvents. There's no events option and no addEvent method. Change your data, then call refresh(), which clears the cache and fetches again.
  3. Every event needs an id for drag and drop, and a valid start and end. Use new Date(2026, 10, 23) or '2026-11-23T09:00' rather than '2026-11-23', which is parsed as UTC midnight and can land on the previous day west of UTC.
  4. The action runs once. Svelte doesn't re-run an action when its parameter changes, so don't pass reactive options and expect the calendar to update. Keep the instance in calendar and call setView(), goToDate() or refresh() from your own buttons or effects.

For dark mode, add the uc-dark class to the container or a parent. Theme colors come from CSS custom properties such as --cal-primary and --cal-event-bg on .uc-calendar. The theming guide covers both.

SvelteKit and TypeScript notes

In SvelteKit, the action itself never runs on the server, but the top-level import does. If you hit SSR errors, follow the client-only patterns in How to Add a Calendar to a SvelteKit Site. With lang="ts", add declare module 'simple-calendar-js'; to a .d.ts file, because the package ships no type definitions.

What it won't do

Be clear about the limits before choosing it as your Svelte scheduler:

  • No resource or timeline views: no rows per person or room. Use EventCalendar (free) or SVAR PRO.
  • No recurring events: expand series into individual events before returning them from fetchEvents.
  • No time zone option: events show in the browser's local time, so convert on the server or before returning them.
  • No built-in editor: onSlotClick and onEventClick open your own form.

Licensing: SimpleCalendarJS is free for personal, educational and open source projects. Client sites, SaaS and internal company tools need a commercial license, one per project (see pricing). You can try the options in the sandbox before installing.

Need a calendar in your app?

SimpleCalendarJS: ~14 KB gzipped, zero dependencies, works in any framework. Free for personal use.

Native Svelte Component vs a Wrapped Vanilla Library

The table splits into two approaches, and the difference matters more than any single feature.

Native components (EventCalendar's Svelte build, SVAR) take options as props and fit runes-style code: change $state and the calendar updates. SVAR also lets you compose its panels and editor as Svelte components. The cost is coupling. If part of your product later moves to React or plain server-rendered pages, you need a different package (SVAR publishes separate React and Vue builds; EventCalendar also has a standalone JS build).

Vanilla libraries mounted with an action (SimpleCalendarJS, DHTMLX, EventCalendar's standalone build) are imperative: you create an instance, hold a reference and call methods. You write about ten lines of glue, and in return the same code and knowledge carry over to any stack. Upgrading Svelte doesn't break the calendar, because it doesn't depend on Svelte internals. That's a real advantage given how many Svelte 3 calendar packages stopped working after the move to Svelte 5.

The Svelte docs note that from Svelte 5.29 you can also use attachments ({@attach}) instead of actions. For a calendar that's created once and destroyed on unmount, either works.

Which Svelte Scheduler Should You Pick?

  1. You need resource rows or a timeline and have no budget: EventCalendar. It's MIT-licensed, maintained, and the resource plugins are included.
  2. You want a ready-made scheduling UI with an editor, in idiomatic Svelte 5: SVAR Svelte Calendar. Budget for PRO if recurrence, resources or date-range loading become requirements.
  3. You mostly display schedules and like the Temporal API: Schedule-X, knowing drag and resize are Premium since v4.
  4. You're an enterprise team that needs a support contract: DHTMLX Scheduler.
  5. You need month/week/day/list with drag, resize and API loading, in a small dependency-free package that also works outside Svelte: SimpleCalendarJS through an action, if its license terms fit your project.

If you're still comparing beyond Svelte-specific packages, Best JavaScript Calendar Libraries in 2026 lists bundle sizes across the wider field.

Sources & Further Reading

Image Credits

Image free to use under the Pexels License.

Frequently Asked Questions

Can I use a vanilla JavaScript calendar in Svelte 5?

Yes. Any calendar that mounts into a DOM element works in Svelte 5. Create it in an action (use:) or in onMount, keep the instance in a variable so you can call its methods, and destroy it when the element unmounts. You don't need a Svelte wrapper, and Svelte's reactivity doesn't conflict with it because the library manages its own DOM.

Should I use an action or an attachment to mount a calendar in Svelte 5.29+?

Both work. The Svelte docs suggest considering attachments ({@attach}) in Svelte 5.29 and newer because they are more flexible and composable, but actions are still supported. For a calendar that gets created once and destroyed on unmount, an action with an $effect teardown is simple and works on every Svelte 5 version.

How do I handle recurring events in a Svelte scheduler?

SVAR Svelte Calendar includes editable recurring events in its paid PRO edition. With most other libraries, you expand the recurrence rule into separate event instances yourself, ideally on the server for the requested date range, and return those instances to the calendar. Store the rule once and generate instances when you load events, rather than storing every occurrence.

How do I avoid SSR errors with a calendar in SvelteKit?

Only create the calendar in the browser. Actions and onMount never run during server rendering, so the calendar's constructor is safe there. If the library touches window or document when it's imported, load it with a dynamic import inside the action or wrap the component in {#if browser}. The SvelteKit guide on this blog walks through both approaches.

Does SimpleCalendarJS have TypeScript types for Svelte projects?

No. The package doesn't ship TypeScript type definitions. In a Svelte project that uses lang="ts", add a .d.ts file containing declare module 'simple-calendar-js'; so the import compiles. The calendar instance and options are then typed as any, so check option names against the docs.

Is there a free Svelte scheduler with resource views?

Yes. EventCalendar by vkurko (@event-calendar/core) is MIT-licensed and includes resource time grid and resource timeline views as plugins. SVAR Svelte Calendar and Schedule-X both put resource views in their paid editions, and SimpleCalendarJS has no resource views.

Add a calendar to your app today

Free for personal projects. $49/year or $199 lifetime per commercial project.

Keep Reading