Is atlaskit deprecated?

Today I wanted to use atlaskit but sadly I noticed that atlaskit is outdated (e.g. styled-components@3). Next I took a look at issues and noticed that the issue-tracker for atlaskit has been removed.

It seems like issues posted here about compatibility and/or the future of atlaskit don’t even get answered (which IMHO is very sad and breaks the idea of maintaining open-source projects).

1 Like

Thanks for reaching out! Atlaskit is most definitely not deprecated - we have a number of internal development teams working on everything from the core component sets, to media and editor. Recently we’ve re-worked our issue tracking experience - however for now it’s been moved back into an internal system while we find a better way to allow external contribution.

Regarding the outdated styled-components dependency, we’re looking into it. The last few months our core team has been focused on converting the project to Typescript, but that work is beginning to wrap up and we’ll be looking into where to go with our CSS-in-JS solution. Currently a few components such as Checkbox and Button have been converted to use a newer version of Emotion, instead of Styled Components 3.


Hey @acampbell3 ,

Can you give update on this? We are on the breaking point where we are going to migrate away from Atlaskit.

As I see latest Atlaskit is still using styled components 3.


1 Like

Hi @Townsheriff,
Thanks for reaching out - could I ask which @atlaskit namespaced components you’re using?

I can confirm that the majority of components supported by the Atlassian Design System team have been recently converted from styled-components to use @emotion/core (or have been converted, but are pending release on NPM in the coming weeks). However I understand this is not all of the components in the @atlaskit namespace, and a number of them remain unconverted.

More information on the Emotion migration work can be found on this ticket (link).

This is what we are using now:

    "@atlaskit/avatar": "^20.4.0",
    "@atlaskit/breadcrumbs": "^11.3.1",
    "@atlaskit/button": "^16.1.0",
    "@atlaskit/checkbox": "^12.2.2",
    "@atlaskit/css-reset": "^6.0.1",
    "@atlaskit/dropdown-menu": "^10.1.8",
    "@atlaskit/form": "^8.2.4",
    "@atlaskit/icon": "^21.8.0",
    "@atlaskit/inline-edit": "^12.1.1",
    "@atlaskit/modal-dialog": "^12.0.1",
    "@atlaskit/page-header": "^10.1.2",
    "@atlaskit/pagination": "^14.0.4",
    "@atlaskit/rating": "^0.1.8",
    "@atlaskit/select": "^15.0.2",
    "@atlaskit/spinner": "^15.1.1",
    "@atlaskit/tabs": "^13.1.4",
    "@atlaskit/tag": "^11.1.3",
    "@atlaskit/textfield": "^5.0.5",
    "@atlaskit/theme": "^11.4.1",
    "@atlaskit/tooltip": "^17.5.0",

and we are forced to use: "styled-components": "^3.4.10", otherwise some components stop working for example dropdown menu click handler is not called (as I recall).


Thanks for that information @Townsheriff, and I hope you had a pleasant new year!
It looks like the following packages need to be upgrade to the versions listed in order to drop the styled-components dependency.

  • @atlaskit/form: 8.4.0
  • @atlaskit/dropdown-menu: 11.0.0
  • @atlaskit/page-header: 10.2.0
  • @atlaskit/theme: 12.0.0

The Styled-components → Emotion migration is now complete for all non-deprecated Design System components (that is, the components on or under the “Design System” heading on the Atlaskit website).

any plans to upgrade the ReactJs version defined in each atlaskit package as peerDependencies? (currently 16.18.0)