V6 Release Notes and Upgrade Guide

This release is currently in BETA and subject to change.

The primary goal of V6 is to solve bugs related to the installation of FullCalendar’s packages. Beyond npm-installing a few different packages and rewriting some import statements, there are no breaking API changes or changes to functionality.

To understand how v6 fits into the larger plan, view the Roadmap »

View the V6 docs »

Third-party Tools

FullCalendar no longer attempts to import .css files. Instead, FullCalendar’s JS is responsible for injecting its own CSS. This solves many issues with third-party tools:

Web Component Package

The Web Components API provide a standardized way to make reusable custom elements. FullCalendar offers a custom element in the new @fullcalendar/web-component package. Learn how to use it »

Import Statements

NOT YET IMPLEMENTED

The ordering of import statements should not matter.

Package Installation

NOT YET IMPLEMENTED

Some FullCalendar packages should be peerDependencies of others.

CSS Customization

NOT YET IMPLEMENTED

Overriding FullCalendar’s CSS variables won’t require any build system configuration.

Improved Vue Support

NOT YET IMPLEMENTED

IE 11 Support

NOT YET IMPLEMENTED

FullCalendar V6 will no longer support IE 11. This will streamline the code and reduce bundle size.

Stop using XHR, use fetch instead.