# RFC-78: Dropping support for React 16 and rendering in a React 18 concurrent root in Jira and Confluence **URL:** \ **Category:** Request for Comments (RFC)\ **Tags:** atlassian-design-system, adg, react, forge-ui-kit, connect, connect-app, custom-ui, design-system, rfc, atlassian-connect, atlaskit\ **Created:** [December 9, 2024, 1:20am UTC](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 "2024-12-09T01:20:31Z")\ **Posts on this page:** 1\ **Showing post:** 22
**Author:** ![KylorHall](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KylorHall](https://community.developer.atlassian.com/u/KylorHall)\ **Post date:** [July 8, 2025, 8:01pm UTC](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/22 "2025-07-08T20:01:02Z")
@pch I’m out of office for a bit and no one is actively owning this area at the moment, just wanted not leave you hanging. I’ll have a proper look when I’m back in August, but likely there’s not much more than I know off the top of my head: - `@atlaskit/badge` uses StrictMode in unit tests (and similar other components likely work) - `@atlaskit/portal` (and the components that use that like Modal, Popup, Calendar, etc) still haven’t landed the fix I alluded to above - `@atlaskit/dynamic-table` uses legacy context, but so may some other Atlaskit components indirectly I don’t know of any app running using React 19 or StrictMode as I’ve given a few Atlassians the same guidance as I’ve given you, so it’s mostly an unknown area for us until we do start looking formally. --- _[View the full topic](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)._