\n\n\n## Tree-shakeable API š³\n\nFor anyone hyper-concerned about bundle size, `temporal-polyfill` also ships an\nalternate function API designed for tree-shaking. Instead of large `Temporal.*`\nclasses, every operation is a standalone function that acts on a plain record,\nso a bundler keeps only the functions you actually import.\n\n```js\nimport * as PlainDateFns from 'temporal-polyfill/fns/PlainDate'\n\nconst date = PlainDateFns.create(2026, 6, 1)\nconst later = PlainDateFns.addMonths(date, 2)\n\nPlainDateFns.toString(later) // '2026-08-01'\n```\n\nš¤ **Building a component library?** The function API is built to be a shared,\ndeletable peer dependency for third-party tools like date pickers and\nschedulers. See [For component authors](https://github.com/fullcalendar/temporal-polyfill/blob/main/docs/fns/for-component-authors.md).\n\nEach Temporal type has its own entrypoint under `temporal-polyfill/fns/*` ā for\nexample `temporal-polyfill/fns/PlainDate` or `temporal-polyfill/fns/ZonedDateTime`.\n\nBest of all, this isn't a one-way door. When the time is right ā once native\n`Temporal` is available in every environment you target, and you no longer need\nthe polyfill ā [temporal-polyfill-codemod](https://github.com/fullcalendar/temporal-polyfill/blob/main/codemod/README.md)\nrewrites your function calls back into idiomatic `Temporal.*` expressions.\nSo `PlainDateFns.addMonths(date, 2)` becomes `date.add({ months: 2 })`,\nwith no manual find-and-replace.\n\nš [**Read the full Tree-shakeable API docs ā**](https://github.com/fullcalendar/temporal-polyfill/blob/main/docs/fns/index.md)\n\nThe docs cover the complete catalog of functions, their TypeScript type exports,\nthe codemod workflow, and how each function maps back to the standard `Temporal`\nAPI.\n","readmeFilename":"README.md"}