React 18 Support for Atlaskit Components

Atlassian Ecosystem Design
,
21

And we need an update up @atlaskit/user-picker…

1 Like
22

Hi all, we’ll share a React 18 roadmap update and an RFC in the following weeks.

As stated previously, we are gradually migrating Atlaskit components to R18 and refactoring them to support modern features like streaming SSR.

While the official R18 support announcement will only happen once all components are refactored and validated, many components already work in concurrent mode. The peer dependency version range is the best way to check each component’s status.

Addressing some of the questions on this thread:

React 19 support plan – Nothing to announce yet. I’d expect us to have a reasonable path to R19, as we have been building the tooling and infra to make large-scale changes more efficient.

dynamic-table - We migrated the dynamic table to pragmatic drag and drop, our new r18 compatible dnd solution. Dynamic table is now R18 compatible.

@atlaskit/tree - The tree component has been deprecated and won’t receive R18 or other updates. We’d recommend moving to another solution.

react-dom version at 16- The devDependency of react-dom will be updated later. We will do this in one go for all components. For dev deps, we maintain a single shared version across all components. For peer deps, we can offer different version ranges.

@atlaskit/user-picker - We will add R18 support to user picker. The roadmap update in a week or two will share more details on when to expect the support to land.

Thanks for the good questions.

6 Likes
23

Hey all, just to cross-post, here is that promised RFC with all the details: RFC-78: Dropping support for React 16 and rendering in a React 18 concurrent root in Jira and Confluence

2 Likes
24

Hello there,

I’m currently looking to migrate a Forge static app to React 18. However, the app depends on @atlaskit/editor-core, which is built on React 16. Overriding the peer dependencies hasn’t resolved the compatibility issues.

Is there an official timeline or roadmap for updating @atlaskit/editor-core to support React 18? Any insights would be greatly appreciated to help plan our migration.

3 Likes
25

Hey @SamiJaatinen

I wanted to check if there are any updates regarding support for React 18+ in @atlaskit/editor-core. I noticed the latest patch release (v203.17.4) includes updated dependencies. Does this version or any upcoming one include React 18+ compatibility?

Thanks!

26

Hi @umang.savaliya ,
Editor-core supports React 18 now. You can see the support range of each component under the peer dependencies in package.json.

We’ll be doing proper comms once we have battle-tested every component in production. It’s getting close :slight_smile:

1 Like
27

Hi @SamiJaatinen
Are we good to use editor-core with React 18 now? Would be great to have official communication on this.

28

Hey @chhantyal apologies, I wasn’t monitoring this thread. The answer is yes, @atlaskit/editor-core only supports React ^18.2.0 now.

I’ll point you to this comment: RFC-78: Dropping support for React 16 and rendering in a React 18 concurrent root in Jira and Confluence - #14 by KylorHall

Quick update—the mentioned peerDependencies change has landed this past week, indicating almost every @atlaskit/* maintained package will no longer allow for a React 16 or React 17 peer dependency. For reference, see @atlaskit/button@21.0.0 from February 24th (as a major to indicate this shift, but with no direct breaking changes).

The expectation with that going forward is Atlassian’s packages only support React 18 (until you see another RFC around React 19, but I have no timeline to share). Additionally, almost all of our tests are using the new React.createRoot() concurrent APIs as that has been our focus.

29

I opened a new topic about React 19 support here, for anyone looking for it: