Skip to content

Releases: Financial-Times/dotcom-page-kit

v12.3.0

27 Jan 17:13
77981b2
Compare
Choose a tag to compare

with this release, n-ui-foundations is deprecated, and what's left of it has moved into dotcom-ui-base-styles. although you can migrate your app from n-ui-foundations to dotcom-ui-base-styles now, there's no migration guide, as there will be a migration script you can run soon.

What's Changed

Full Changelog: v12.2.1...v12.3.0

v12.2.1

27 Jan 12:03
bd984a1
Compare
Choose a tag to compare

What's Changed

Full Changelog: v12.2.0...v12.2.1

v11.3.1

27 Jan 12:03
22b2a26
Compare
Choose a tag to compare

What's Changed

Full Changelog: v11.3.0...v11.3.1

v11.3.1-beta.0

24 Jan 11:41
Compare
Choose a tag to compare
v11.3.1-beta.0 Pre-release
Pre-release

Full Changelog: v11.3.0...v11.3.1-beta.0

v12.2.0

23 Jan 15:49
faa3181
Compare
Choose a tag to compare

What's Changed

Full Changelog: v12.1.0...v12.2.0

v12.1.0

22 Jan 14:43
2f6aac2
Compare
Choose a tag to compare

What's Changed

  • CPP-2222 Use Webpack's native import resolution for S/CSS and drop Postcss by @ivomurrell in #1123

Full Changelog: v12.0.1...v12.1.0

v12.0.1

21 Jan 17:59
93ecbd5
Compare
Choose a tag to compare

What's Changed

Full Changelog: v12.0.0...v12.0.1

v12.0.0 - Webpack 5

20 Jan 16:23
b4016a6
Compare
Choose a tag to compare

This release updates Page Kit's Webpack plugins to Webpack 5. You'll need to update your app to Webpack 5 when updating to this version of Page Kit. Most apps (i.e. ones using Page Kit plugins without any additional custom Webpack configuration) will be able to just update the packages and everything will be fine. If you have any custom Webpack config, follow the Webpack 5 migration guide.

When updating to Webpack 5, you may need to be aware of its breaking changes. In testing, I've found one breaking change that affects apps:

  • when a package has an exports specifier in package.json Webpack 5 is strict about not importing things that aren't exported in exports. this may require code changes in packages and/or apps to export everything that should be and import things correctly.
    • for example, next-article imports @financial-times/custom-code-component/dist/custom-code-component.js, but that package doesn't include that entrypoint in its exports (it exports ., the top-level import, pointing that at the file dist/custom-code-component.js, which isn't visible outside the package). next-article won't build with Webpack 5 without changing that import to @financial-times/custom-code-component.

This release contains a number of other breaking changes:

  • We no longer use Autoprefixer. The CSS we write is supported in every browser we use, and browsers no longer use vendor prefixes for new features. The only holdouts are a handful of -webkit prefixed properties supported by every browser; i have verified via Github search that we never use any of these properties unprefixed.
  • Our Babel config now targets the latest Browserslist default config. This is Browserslist best practice, slightly lenient than our current browser support policy, results in much smaller Babel output than our previous Browserslist config (which was inadvertently targeting some very old browsers), and means we don't have to keep updating the config.
  • The prependData option in dotcom-build-sass, which was deprecated in favour of additionalData, has been removed.

What's Changed

⚠️ BREAKING CHANGES

New Contributors

Full Changelog: v11.3.0...v12.0.0

v11.3.0

03 Jan 12:35
77a5bc4
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v11.2.1...v11.3.0

v11.2.1 - Support GTM first-party mode

30 Oct 16:10
2ccf86d
Compare
Choose a tag to compare

What's Changed

Full Changelog: v11.2.0...v11.2.1