A logo is a visual representation of a brand or product. It can be a word or an image, or a combination of both.
yarn add @atlaskit/logo#117363
10a0f7f6c2027 -
This package's peerDependencies have been adjusted for react and/or react-dom to reflect the
status of only supporting React 18 going forward. No explicit breaking change to React support has
been made in this release, but this is to signify going forward, breaking changes for React 16 or
React 17 may come via non-major semver releases.
Please refer this community post for more details: https://community.developer.atlassian.com/t/rfc-78-dropping-support-for-react-16-and-rendering-in-a-react-18-concurrent-root-in-jira-and-confluence/87026
3ef7f182f166b -
[ux] Updated Atlassian Analytics logo and icon to support iconColor and textColor to align
with others.ed68a8d2ee5f7 -
Update dependencies and remove unused exports and codemods.4660ec858a305 -
Update React from v16 to v18#170937
2f502fec31157 -
Migrated from @emotion/react to @compiled/react in order to improve performance, align with
the rest of the Atlaskit techstack, and support React 18 Streaming SSR.
Please note, in order to use this version of @atlaskit/logo, you will need to ensure that your
bundler is configured to handle .css imports correctly. Most bundlers come with built-in support
for .css imports, so you may not need to do anything. If you are using a different bundler,
please refer to the documentation for that bundler to understand how to handle .css imports.
57f451bda8919 -
Adds side-effect config to support Compiled css extraction in third-party apps3c4de48168ffe -
Update the import path of useId* from @atlaskit/ds-lib#127511
db30e29344013 -
Widening range of react and react-dom peer dependencies from ^16.8.0 || ^17.0.0 || ~18.2.0
to the wider range of ``^16.8.0 || ^17.0.0 || ^18.0.0` (where applicable).
This change has been done to enable usage of react@18.3 as well as to have a consistent peer
dependency range for react and react-dom for /platform packages.
c733254a2dd6e -
Explicitly set jsxRuntime to classic via pragma comments in order to avoid issues where jsxRuntime
is implicitly set to automatic.#93481
fb0aacf8c8957 -
Updates product logos following a brand refresh, cleaning up the feature flag from 13.17.0. This
release also deletes a number of deprecated logos and props, and marks other logos as deprecated.
iconGradientStart and iconGradientStop props have been removed from all Icon and Logo
components. Updated logos do not support gradients.Wordmark components have been removed. These wordmarks were only designed for use
in a legacy navigation pattern which is no longer supported. If you are using these components,
you should replace them with the appropriate Logo component.HipchatLogo and HipChatIconStrideLogo and StrideIconJiraCoreLogo and JiraCoreIconJiraServiceDeskLogo and JiraServiceDeskIconOpsGenieLogo and OpsGenieIcon (old versions of OpsgenieLogo and OpsgenieIcon)AtlasLogo and AtlasIconAtlassianStartLogoHalpLogo and HalpIconJiraSoftwareLogo and JiraSoftwareIcon - use JiraLogo and JiraIcon insteadJiraWorkManagementLogo and JiraWorkManagementIcon - use JiraLogo and JiraIcon instead428f67898ecb -
[ux] Adding product logos for Guard, Rovo, Atlassian Marketplace, Atlassian Admin, Atlassian
Administration, and Atlassian Access. Testing some other glyphs behind a feature flag, if
successful these changes will be enabled in a future release.d6c368b4b3e5 -
[ux] This release updates some glyph, colour and theming behaviour changes.89925a9d50b2 -
[ux] This release tests some Jira Align and Atlas glyph, colour and theming behaviour changes
behind a feature flag. If successful, these changes will be enabled in a future release.57d3c407b13c -
[ux] This release tests some glyph, colour and theming behaviour changes behind a feature flag. If
successful, these changes will be enabled in a future release.4ae083a7e66 - Use
@af/accessibility-testing for default jest-axe config and jest-axe import in accessibility
testing.e7ea6832ad2 - Bans the
use of React.FC/React.FunctionComponent type in ADS components as part of the React 18 migration
work. The change is internal only and should not introduce any changes for the component
consumers.b1bdec7cce2 - Internal
change to enforce token usage for spacing properties. There is no expected visual or behaviour
change.56507598609 - Skip
minor dependency bump4d2e52e86d3 - [ux] Add
Atlassian Analytics logo and icon. Also fixes a bug with non-unique linear-gradient ids where
subsequent logos on a page could be impacted by display/vvisibility styles applied to the first
logo on a page.261420360ec - Upgrades
component types to support React 18.b77d5924c19 - [ux]
Remove "width" attribute from Jira Product Discovery logo and icon SVGs.88a34a8c2dd - Remove
redundant role=presentation on wrapping @atlaskit/icon and @atlaskit/logo spans.68e771a783a - Updates
@emotion/core to @emotion/react; v10 to v11. There is no expected behavior change.76eadca8ef3 - Adds
Jira Align logo, icon and wordmark.d448e04e6a8 - [ux]
Internal changes to make the styling more resilient to inherited styles.c320954edd7 - Internal
code change turning on new linting rules.#22642
c7c2083475d - [ux] -
Adds appearance prop that allows you to choose between three brand-approved appearances:
brand, neutral and inverse. These will be based on design tokens and theme-responsive.
iconColor, iconGradientStart, iconGradientEnd and textColor props. They
will still be supported in the immediate future but the goal is to shift usages towards using
the appearance prop.#21570
0793be315f4 - [ux]
This is an update to clearly mark all deprecated Logo exports as deprecated and slated for removal
in the next major release. In the next verion we will be removing the following deprecated exports
from the main entrypoint:
StrideIcon, StrideLogo, StrideWordmarkHipchatIcon, HipchatLogo, HipchatWordmarkJiraCoreIcon, JiraCoreLogo, JiraCoreWordmark (use JiraWorkManagement +
Icon|Logo|Wordmark instead)JiraServiceDeskIcon, JiraServiceDeskLogo, JiraServiceDeskWordmark (use
JiraServiceManagement + Icon|Logo|Wordmark instead)OpsGenieIcon, OpsGenieLogo, OpsGenieWordmark (use Opsgenie with a lowercase 'g' +
Icon|Logo|Wordmark instead)We will also be removing the following deprecated exports from the @atlaskit/logo/constants
entrypoint:
Props (use LogoProps instead)
DefaultProps (use defaultLogoParams instead)
To help with this migration, we have provided a codemod that you can run to automatically update your imports (it will leave a comment if you are using a logo with no alternative). This codemod has been around for a while, but we've updated it in this release.
Once you've upgraded @atlaskit/logo, use the Atlaskit codemod CLI. See
documentation on DAC for
general codemod guidance.
Without setting options in your terminal command, you can run the following and type to search for
logo and select @atlaskit/logo: 13.6.0-rename-imports from the interactive CLI.
npx @atlaskit/codemod-cli [TARGET_PATH]`
For a TypeScript codebase, a more detailed command might look something like this.
npx @atlaskit/codemod-cli --ignore-pattern node_modules --parser tsx --extensions js,jsx,ts,tsx ./packages
For a Flow codebase, you will want to use --parser babylon instead of --parser flow.
4caed6d5063 -
Refactors logo converting it from class components to functional components. This includes file
renames and some API changes such as prop name changes but is still backwards compatible. These
old APIs will be deprecated in a later release.ec464e07b10 - Fixes a
bug where the Atlassian Start logo did not render correctly on Firefoxaf4bca32ad4 - Internal
changes to supress eslint rules.83a089fe0cc - Halp has
been added to logos. This includes the logo, wordmark and icon.cc0c678724c - Add
default label for Logo#10230
0017d2a8439 - Since
the logo, icon and workmard components of JiraCore, JiraServiceDesk, OpsGenie, Stride and Hipchat
are deprecated in @atlaskit/logo, we provided a codemod to help consumers upgrade their
components.
Running the codemod cli
To run the codemod: You first need to have the latest avatar installed before you can run the codemod
yarn upgrade @atlaskit/logo
Once upgraded, use the Atlaskit codemod-cli;
npx @atlaskit/codemod-cli --parser [PARSER] --extensions [FILE_EXTENSIONS] [TARGET_PATH]
Or run npx @atlaskit/codemod-cli -h for more details on usage. For Atlassians, refer to this doc
for more details on the codemod CLI.
Updated dependencies
5f44a31b58a - [ux] Add
new Trello logo, Atlassian Start logo and Compass logo to @atlaskit/logo#9756
c8afaa49d34 - Add
OpsgenieIcon, OpsgenieLogo and OpsgenieWordmark in order to rename OpsGenie to Opsgenie,
and deprecate the following logos:
JiraCoreIcon, JiraCoreLogo, JiraCoreWordmarkJiraServiceDeskIcon, JiraServiceDeskLogo, JiraServiceDeskWordmarkStrideIcon, StrideLogo, StrideWordmarkHipchatIcon, HipchatLogo, HipchatWordmark471e2431a7c -
Downgrade back to date-fns 1.30.1 We discovered big bundle size increases associated with the
date-fns upgrade. We're reverting the upgarde to investigate952019cfd39 - Removed
extraneous/unnecessary dependencies for design system components.dfa1827ecad - Fixed
the broken "Download the logos" link on https://atlassian.design/components/logo/usagece8c85a20d - As part of
this task we have introduced a new JSM logo and deprecated JSD logo5f58283e1f - Export
types using Typescript's new "export type" syntax to satisfy Typescript's --isolatedModules
compiler option. This requires version 3.8 of Typescript, read more about how we handle Typescript
versions here: https://atlaskit.atlassian.com/get-started Also add typescript to
devDependencies to denote version that the package was built with.7315203b80 - Rename
AkCode and AkCodeBlock exports to Code and CodeBlock for @atlaskit/code.#3885
6c525a8229 - Upgraded
to TypeScript 3.9.6 and tslib to 2.0.0
Since tslib is a dependency for all our packages we recommend that products also follow this tslib upgrade to prevent duplicates of tslib being bundled.
954cc87b62 - The readme
and package information has been updated to point to the new design system website.ce3b100bed - Change the
Atlassian Icon for better alignment with other Iconsdb053b24d8 - Update all
the theme imports to be tree-shakable87f4720f27 - Officially
dropping IE11 support, from this version onwards there are no warranties of the package working in
IE11. For more information see:
https://community.developer.atlassian.com/t/atlaskit-to-drop-support-for-internet-explorer-11-from-1st-july-2020/3953454a9514fcf - Build and
supporting files will no longer be published to npm[patch]f6667f2909:
Change imports to comply with Atlassian conventions- Updated dependencies 6b8e60827e:
Updated dependencies 449ef134b3:
Updated dependencies f7f2068a76:
Updated dependencies 57c0487a02:
Updated dependencies 6efb12e06d:
[patch]fd5292fd5a:
Corrects accessibility behavior for wrapping span. It now will now:
aria-label if label is definedrole to either img if label is defined, or presentation if it is
not defined- Updated dependencies
66dcced7a0:Updated dependencies eea5e9bd8c:
[patch]6548261c9a:
Remove namespace imports from React, ReactDom, and PropTypes- Updated dependencies 6548261c9a:
[patch]30acc30979:
@atlaskit/select has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided. No API or behavioural changes.
[patch]35d2229b2a:
Adding missing license to packages and update to Copyright 2019 Atlassian Pty Ltd.
[patch]097b696613:
Components now depend on TS 3.6 internally, in order to fix an issue with TS resolving non-relative imports as relative imports
[minor]b81d931ee3:
Added new OpsGenie logo, fixed the gradient for the StatusPage logo, and refactored atlassian-switcher to use the new logos
[patch]b0ef06c685:
[major]4b07b57640:
[major]7c17b35107:
[patch]e04a402953:
[major]76299208e6:
As a breaking change, all @atlaskit packages will be dropping cjs distributions and will only
distribute esm. This means all distributed code will be transpiled, but will still contain
import and export declarations.
The major reason for doing this is to allow us to support multiple entry points in packages, e.g:
import colors from `@atlaskit/theme/colors`;
Previously this was sort of possible for consumers by doing something like:
import colors from `@atlaskit/theme/dist/esm/colors`;
This has a couple of issues. 1, it treats the file system as API making internal refactors harder, we have to worry about how consumers might be using things that aren't actually supposed to be used. 2. We are unable to do this internally in @atlaskit packages. This leads to lots of packages bundling all of theme, just to use a single color, especially in situations where tree shaking fails.
To support being able to use multiple entrypoints internally, we unfortunately cannot have multiple distributions as they would need to have very different imports from of their own internal dependencies.
ES Modules are widely supported by all modern bundlers and can be worked around in node environments.
We may choose to revisit this solution in the future if we find any unintended condequences, but we see this as a pretty sane path forward which should lead to some major bundle size decreases, saner API's and simpler package architecture.
Please reach out to #fabric-build (if in Atlassian) or create an issue in Design System Support (for external) if you have any questions or queries about this.