Sunflower 2025-R1 release notes
timeline
bump major versions of stripes-* 2025-02-03
bump major version of react-intl 2025-02-03
commit breaking change to stripes-* beginning 2025-02-05
third-party breaking changes
react-intl v7: no impact; we’re upgrading but don’t expect any fallout. repos will need to update the dependency version but that’s it. STRIPES-960
stripes-* breaking changes
stripes-core: remove legacy (non-rtr) authentication (low impact) STCOR-918, STCOR-922
stripes-components: remove long-deprecated props (low impact) STCOM-1398
stripes-webpack: remove deprecated serviceworker (no impact) STRWEB-125
stripes-util: remove deprecated functions (low impact) STUTL-16
stripes-components: remove react-overlays STCOM-1339, STCOM-1336
transpilation: replace existing
transpile
command in stripes-cli with a command that actually transpiles (instead of bundling, which the current command does). We will begin actually publishing transpiled modules in Trillium but that won’t matter if you’re only consuming public exports. IOW, think of this is an operational change not a functional one, just like migrating from local GA workflows to shared GA workflows was.
future work
migrate from moment to dayjs (medium impact) STRIPES-699
If you’re manipulating dates independent of stripes-components, migrate to dayjs now by importing it from
@folio/stripes/components
. There are some narrow special-cases with stripes-components, e.g. using DatePicker with excluded dates, that still require using moment, but these are rare. If you are using moment just for formatting, use react-intl instead. It is purpose-built to handle this (docs for components and imperative functions). If you’re legit doing date-manipulation, then it’s time to file a story to migrate from moment to dayjs. We won’t remove moment in Sunflower, but will do so in a near-future release and want to get the migration underway ASAP.