# React 19 Support for Atlaskit Components

**URL:** <https://community.developer.atlassian.com/t/react-19-support-for-atlaskit-components/92166>\
**Category:** Atlassian Ecosystem Design\
**Tags:** atlaskit\
**Created:** [May 20, 2025, 8:42am UTC](https://community.developer.atlassian.com/t/react-19-support-for-atlaskit-components/92166 "2025-05-20T08:42:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![KylorHall](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KylorHall](https://community.developer.atlassian.com/u/KylorHall)\
**Post date:** [May 20, 2025, 10:10pm UTC](https://community.developer.atlassian.com/t/react-19-support-for-atlaskit-components/92166/4 "2025-05-20T22:10:14Z")

</div>

I’ve commented on React 19 [in the React 18 RFC](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/13), but it’s been more more than 5 months, so it’s fair to say a bit more.

There’s been no change in support or new plans for React 19, I can say it’s being discussed, but the timeframe between even a successful spike and landing that to Atlaskit would be multiple months, so I can pretty confidently say this wouldn’t land in 2025.

What I’m hoping for at the least is wider levels of `React.StrictMode` support as we clean up some technical debt from our React 18 migration, which for many packages will mean React 19 support (I’m not certain about the TypeScript error though), as today you will hit things like legacy context in all popups, modals, etc., and other blockers.

I’d say watch out for an RFC around React 19 similar to how we did with React 18, but I wouldn’t expect that to land this year.

---

_[View the full topic](https://community.developer.atlassian.com/t/react-19-support-for-atlaskit-components/92166)._
