Client-side Extensions
Common Internal components
Base components used internally shared across the other packages for the client-side extensions.
Refer to the official documentation for more information.
[5.1.0] - 2025-08-07
IMPORTANT
In order to use this version, you will need to ensure that your bundler is configured to handle .css
imports correctly. This is caused by Atlaskit components migration from runtime @emotion/react
to @compiled/react
. Atlaskit components are now bundled with static CSS instead of runtime styles.
Most bundlers come with built-in support for .css imports, so you may not need to do anything. However if you are using webpack
additional configuration will be required. You can take a look at the suggested webpack setup here.
If you are using a different bundler, please refer to the documentation for that bundler to understand handling .css
imports.
Added
- DCA11Y-1988
ModalHandler
header and ExtensionPointInfo
modal header now renders a CloseButton
- DCA11Y-1988 Introduced StrictMode to React components
- DCA11Y-1988 Added
@atlaskit/heading@5.2.3
and @atlaskit/tokens@5.6.0
to @atlassian/clientside-extensions-components
Changed
- DCA11Y-1988 Updated Node.js engine requirement to
>=20.18.1
from >=20.16.0
.
- DCA11Y-1988 Upgraded atlaskit components including
@atlaskit/button
& @atlaskit/modal-dialog
- DCA11Y-1988 Removed
@atlaskit/theme
package from @atlassian/clientside-extensions-components
package. Replaced deprecated colors with design tokens equivalents
- DCA11Y-1988 Updated
ExtensionPointInfo
component to use design tokens, fixing dark theme compatibility
- BESECART-3480 Update dependencies to use @atlassian/webresource-webpack-plugin instead of atlassian-webresource-webpack-plugin