DayPilotThe JavaScript Scheduler combines its scheduling interactions, date handling, and default appearance in a self-contained core. It can be delivered directly to a browser or used through a framework distribution, with additional libraries needed only for the optional features that use them.
Self-Contained JavaScript Delivery
For script-tag integration, daypilot-all.min.js supplies the DayPilot classes in one minified file. The default Scheduler theme is embedded, so the initial view does not require a separate theme stylesheet. TypeScript declarations are included for typed projects.
The core has no required external JavaScript dependencies. It does not need another date library, a drag-and-drop package, or a framework runtime to display and edit a schedule. A page using several DayPilot components can share the library include.
Framework and npm Distributions
JavaScript and TypeScript projects can use the JavaScript npm distribution, while Angular, React, and Vue applications have matching distributions with native components.
These are framework distributions, not separate npm packages for each scheduling component. Their dependency and framework requirements are distinct from the standalone core. The package manifest describes the requirements of the installed version; the public software bill of materials describes the dependency categories.
Lite packages are published under the @daypilot/daypilot-lite-* namespace on public npm. Pro installations use direct package URLs from npm.daypilot.org.
Optional Export Dependencies
Normal scheduling does not require an Excel or PDF library. Excel export uses ExcelJS, supplied separately by the application. PDF examples compose Scheduler images using a PDF library such as jsPDF. The client-side export documentation describes the image and composed-output options.
Applications can keep these optional tools separate from the initial scheduling view and load them where they are used. Supplied or generated CSS themes are separate assets too; the theme overview explains the choices beyond the embedded default.
Bundle Size and Runtime Work
The delivered size depends on the selected distribution, release, compression, bundler, and optional application code. A script-tag bundle and a framework application build therefore have different delivery characteristics. Use current package and build information when evaluating footprint; figures from an older release do not describe every application.
Download size is also separate from the amount of schedule data and UI content in the browser. Progressive rendering and dynamic loading address large resource lists, event sets, and timelines; see the large-data overview.