@atlassian/react-compiler-gating@^0.2.0 is not in this registry

Forge Forge UI Kit and Custom UI
1

Hi,

My package.json looks like this:

{
  "dependencies": {
    "@forge/api": "8.0.0",
    "@forge/bridge": "6.0.0",
    "@forge/events": "3.0.0",
    "@forge/kvs": "2.0.0",
    "@forge/react": "12.0.0",
    "@forge/resolver": "2.0.0",
    "p-limit": "7.3.0",
    "react": "18.3.1"
  }
}

npm i returns:

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @atlaskit/analytics-next-stable-react-context@1.0.1
npm warn Found: react@18.3.1
npm warn node_modules/react
npm warn   react@"18.3.1" from the root project
npm warn   51 more (@forge/react, @atlaskit/tokens, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer react@"^16.8.0" from @atlaskit/analytics-next-stable-react-context@1.0.1
npm warn node_modules/@atlaskit/analytics-next-stable-react-context
npm warn   @atlaskit/analytics-next-stable-react-context@"1.0.1" from @atlaskit/analytics-next@12.0.1
npm warn   node_modules/@atlaskit/analytics-next
npm warn
npm warn Conflicting peer dependency: react@16.14.0
npm warn node_modules/react
npm warn   peer react@"^16.8.0" from @atlaskit/analytics-next-stable-react-context@1.0.1
npm warn   node_modules/@atlaskit/analytics-next-stable-react-context
npm warn     @atlaskit/analytics-next-stable-react-context@"1.0.1" from @atlaskit/analytics-next@12.0.1
npm warn     node_modules/@atlaskit/analytics-next
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: react-scrolllock@5.0.1
npm warn Found: react@18.3.1
npm warn node_modules/react
npm warn   react@"18.3.1" from the root project
npm warn   51 more (@forge/react, @atlaskit/tokens, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer react@"^16.3.0" from react-scrolllock@5.0.1
npm warn node_modules/react-scrolllock
npm warn   react-scrolllock@"^5.0.1" from @atlaskit/modal-dialog@16.0.1
npm warn   node_modules/@atlaskit/modal-dialog
npm warn
npm warn Conflicting peer dependency: react@16.14.0
npm warn node_modules/react
npm warn   peer react@"^16.3.0" from react-scrolllock@5.0.1
npm warn   node_modules/react-scrolllock
npm warn     react-scrolllock@"^5.0.1" from @atlaskit/modal-dialog@16.0.1
npm warn     node_modules/@atlaskit/modal-dialog
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@atlassian%2freact-compiler-gating - Not found
npm error 404
npm error 404  '@atlassian/react-compiler-gating@^0.2.0' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /Users/***/.npm/_logs/2026-06-23T19_44_11_254Z-debug-0.log

Any ideas?

2

The version numbers do not use a caret (^) - so you’ll exactly be on those versions. You might considers updating a few of these versions. I’d guess that the wrongly linked transitive dependency it’s complaining about is gone after a certain package update. Also I recommend pnpm as a package manager.

Good luck,
Julian

3

That looks like a bug in @forge/react version 12 (latest version, released two days ago). This version can’t be installed because of the missing @atlassian/react-compiler-gating dependency. ADS components are also affected. For example, installing @atlaskit/link with npm i @atlaskit/link causes the same error.

4

I can confirm that the issue is introduced by "@forge/react": "12.0.0". It works with 11.17.0. I was hoping to get rid of the vulnerable uuid dependency by updating @forge/react. Is this the right place to notify Atlassian about the issue? I guess I open a ticket as well.

5

Hi,

+1 with this problem, @forge/react@12.0.0 and some of newer @atlaskit packages (e.g. checkbox) won’t update.

Also I recommend pnpm as a package manager.

Me too, I’m using it for all my Forge apps, but it doesn’t make any difference in this case.

Cheers

6

I can also confirm that this happens for basically every new major version of the @atlaskit component packages, as well as for @atlaskit/adf-schema (55.x.x and higher) and @atlaskit/adf-utils (20.x.x and higher)

7

Hi, we are experiencing the exact same issue here. The error pops up when we try to install @atlaskit/button version ^24.1.1 using Yarn 4.

8

Hi, we are experiencing the same issue. We’ve updated all @forge/* dependencies according to https://developer.atlassian.com/changelog/#CHANGE-3285. We use yarn 4.

9

I have an open ticket with the support…

They claimed it was fixed but not yet.

For those who don’t understand what is happening. They upgraded several @atlaskit packages.

In that upgrade they dragged an internal package: @atlassian/react-compiler-gating.

An example of it is @atlaskit/tokens.

At the time of writing this message, this url shows you this:

image
image1100Ă—418 35.2 KB

And @forge packages depends on @atlaskit packages.

10

According to support, Atlassian dev teams are working on it.

11

Hey all,

We recognise this issue isn’t fixed yet. We are actively working on this to get this fixed soon.

12

At least we didn’t get a ticket created and a request to vote to rank up the severity

13

Hey all,

This issue is now resolved. The @atlassian/react-compiler-gating package has been published to the npm registry, and installs should be working normally again.

A recent update to several @atlaskit packages introduced a dependency on @atlassian/react-compiler-gating, which is an internal package that had not yet been published to the public npm registry. This caused E404 errors when installing @forge/react@12.0.0, newer @atlaskit component packages, and related ADF packages.

We merged a fix and ran our publish pipeline to ensure the missing package is now available on the registry.

What you need to do: Clear your package manager cache and re-run your install command (npm install, yarn install, or pnpm install). Everything should resolve cleanly now.

Thanks,

Sudharsanam

14

I can confirm that the issue is resolved. Thanks!