v11.0.0

Warning

This release drastically strips back unused/little-used functionality from n-ui-foundations as a precursor to moving what's left into Page Kit's dotcom-ui-base-styles. There are a number of changes that could be breaking changes in your app; check the PRs for the breaking change commits listed below for details. There is no migration guide for this version; there will be a migration script when everything has moved to dotcom-ui-base-styles, but updating to this version will make the migration to dotcom-ui-base-styles easier for you.

What's Changed

• Remove polyfill.io from Karma config by @rowanmanning in #169
• Delete .github/settings.yml by @apaleslimghost in #170
• refactor: don't duplicate the o-normalise helpers by @apaleslimghost in #171
• Remove code splitting mixins by @apaleslimghost in #174
• Deprecate javascript utils by @apaleslimghost in #177

⚠️ Breaking Changes

• feat!: remove unused legacy n-ui-configured variable by @apaleslimghost in #175
• feat!: remove image mixin by @apaleslimghost in #172
• feat!: remove $spacing-unit by @apaleslimghost in #173
• feat!: remove default html font size by @apaleslimghost in #176

Full Changelog: v10.1.0...v11.0.0

v10.1.0 - Add support for Node 18

What's Changed

• Update to node 18 by @ivomurrell in #165

Full Changelog: v10.0.0...v10.1.0

v10.0.0

This release is part of the Platforms and Reliability set of scheduled breaking change releases in April.

The breaking changes in this package release are:

• Dropping support for Node.js 14

This will not be a breaking change for your application if it:

• Already runs on Node.js 16

If this is a breaking change for your application because it does not yet run on Node 16 you can follow this guide to migrate from Node.js 14 to Node.js 16

v9.1.0: Upgrade Origami dependencies

What's Changed

• Add npm-publish-token CircleCI context by @serena97 in #143
• removed o-assets-global-path referece by @diegoFernandoMauroFT in #145
• update config for nightly scheduled-pipelines by @serena97 in #146
• Update Origami components by @kavanagh in #149

New Contributors

• @diegoFernandoMauroFT made their first contribution in #145
• @kavanagh made their first contribution in #149

Full Changelog: v9.0.0...v9.1.0

Delete transitive dependencies

The superstore, superstore-sync, and ftdomdelegate packages have been removed from n-ui-foundations' list of dependencies. These dependencies weren't being used in n-ui-foundations at all, but were being used by dependants of the package instead of explicitly declaring these packages as dependencies of the dependant.

You should check to make sure that your package wasn't depending on n-ui-foundations' copies of these dependencies before updating. The simplest way to check is to grep for the packages in your source code to see if any require statements pull them in. If they do then you will need to manually install the ones you need into your package.json as part as the upgrade process to v9.0.0, e.g., via npm install superstore. We have a spreadsheet of packages that might be affected here. You might also find it useful to use the eslint-plugin-import plugin for ESLint with the no-extraneous-dependencies rule enabled to catch issues like this in the future.

Move Origami Components to Peer Dependencies

• moves origami components to be peerDependencies

• adds origami components as devDependencies for local development

• requires NPM 7

v7.0.2: fix engines compatibility issues

What's Changed

• Fix issues with engines enforcement by @ivomurrell in #121

Full Changelog: v7.0.1...v7.0.2

v7.0.1: adds ftdomdelegate, superstore & syperstore-sync

Readds these dependencies that were unintentionally removed during the Bower to NPM migration

v7.0.0: Migrate Bower to NPM

• removes bower and installs dependencies using npm
• deletes resolution-buster file

Remove chai + mocha from dependencies

mocha and chai are now included as devDeepndencies rather than dependencies.

The versions being used were reported by Snyk as allowing a Prototype Pollution vulnerability. Although any consuming apps very unlikely to utilise chai or mocha in a way that would include it as production code (in fact this would probably be very hard to achieve), this new release has been issued so as to make clear the intent that given the knowledge of these vulnerabilities, these libraries should in no way be considered dependencies.