Releases: Financial-Times/dotcom-page-kit
v9.3.2
v9.3.1
v9.3.0
What's Changed
Add sass build time monitoring [OR-483] by @notlee in #1020
Understanding the impact of slow Sass builds will help us prioritise optimisations and/or move away from Sass more quickly (inline with the TGG proposal).
Please set the following environment variables for local development, via Doppler, so we can monitor Sass build times for your projects and aggregate build times across teams.
FT_SASS_STATS_MONITOR
- Set to on
to enable remote logging on build times.
FT_SASS_BIZ_OPS_API_KEY
- A Biz-Ops Metrics API Key for your system.
FT_SASS_BIZ_OPS_SYSTEM_CODE
- The system code of your project.
That will let us monitor sass build times for your projects and aggregate build times across teams!
You'll also see a message locally letting you know how long you’ve been waiting for Sass in total, across builds 🤯
Full Changelog: v9.2.1...v9.3.0
v9.2.1
What's Changed
- CPP-1757: loosen appContext.contentType schema by @apaleslimghost in #1022
Full Changelog: v9.2.0...v9.2.1
v9.2.0
v9.1.1 Remove unnecessary peer dependencies (n-topic-search) for code splitting
What's Changed
- fix: Remove unnecessary peer dependencies (n-topic-search) for code splitting by @GlynnPhillips in #1019
Full Changelog: v9.1.0...v9.1.1
v9.1.0 - header changes for experimental Account / myFT entry test
What's Changed
- Account and myFT entry points test by @GlynnPhillips in #1017
Full Changelog: v9.0.3...v9.1.0
Remove unnecessary peer dependencies from dotcom-build-code-splitting
What's Changed
- fix: Remove unnecessary peer dependencies for code splitting by @GlynnPhillips in #1018
New Contributors
- @GlynnPhillips made their first contribution in #1018
Full Changelog: v9.0.2...v9.0.3
Point to declaration files instead of TypeScript source
What's Changed
- Support n-ui-foundations v10 by @benwallman in #1013
- CPP-1802 Correctly point to declaration files instead of TypeScript source by @ivomurrell in #1016
Full Changelog: v9.0.1...v9.0.2
React 17 support
N.B. Release notes added on 13/11/23
In theory there's no issues upgrading from React 16 to React 17. https://legacy.reactjs.org/blog/2020/10/20/react-v17.html
I've marked this as a major version bump purely because it will cause some projects to break. Anything with a hardcoded dependency on React 16, specifically. Locally this can be avoided with the legacy-peer-deps flag, but ultimately the only answer with dependencies is to keep them up to date (as React 17 is 3 years old, it's still not up to date...)
Some libraries which are deprecated (e.g. Enzyme) don't support React 17 out the box, but there are usually workarounds (e.g. https://stackoverflow.com/questions/64658031/which-enzyme-adapter-works-with-react-17).
Also any teams which are struggling with this update please let me know and I'll be happy to pair to get this sorted.