1import{a as t,f as l}from"./BsBeZ0BT.js";import"./XfYi555m.js";import{a8 as r}from"./BmGYDir5.js";const i={title:"React & TypeScript Innovations in V5 Beta",date:"2020-05-20T08:07:26.000Z",advancedSidebar:!0,description:"FullCalendar v5.0.0-beta.3 has just been released! Updates:"},{title:d,date:h,advancedSidebar:p,description:u}=i;var o=l(`<p>FullCalendar v5.0.0-beta.3 has just been released! Updates:</p> <ul><li><p><strong>âRealâ React</strong> - FullCalendarâs React package is more than just a connector that wraps a vanilla JS lib. It 2actually uses the real React virtual DOM through and through. This is possible because we chose to use Preact 3as FullCalendarâs tiny inner core (more info in a <a href="/blog/2020/02/changes-in-the-upcoming-v5">previous post</a>). 4For the React package, we swap it out for React. This was rather technically difficult to achieve, so Iâll likely 5be writing a blog post about this in the future.</p></li> <li><p><strong>TypeScript</strong> - The TypeScript definitions have been infinitely improved over the previous beta release. They 6are now baked into the core code in such a way that they will never fall out of date.</p></li> <li><p><strong>Small Bugs</strong> - For more info, <a href="https://github.com/fullcalendar/fullcalendar/blob/master/CHANGELOG.md" rel="nofollow">view the full changelog</a></p></li></ul> <p>Weâre getting very close an official v5! We just need to fix printer-friendly rendering and then weâre off to the races!</p> <ul><li><a href="https://legacy.fullcalendar.io/v5/upgrading-from-v4" rel="nofollow">View the Changelog and Upgrade Guide</a></li> <li><a href="/docs">View the Docs</a></li> <li><a href="/docs/getting-started">Get the Code</a></li></ul>`,1);function f(e){var a=o();r(6),t(e,a)}export{f as default,i as metadata};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.