@atlaskit/editor-common : No matching version found for relay-runtime@0.0.0-main-39e79f66

Forge Forge UI Kit and Custom UI
1

Dear,

We’re getting an error while importing "@atlaskit/editor-common":"^111.8.12":

No matching version found for relay-runtime@0.0.0-main-39e79f66 while fetching it from https://registry.npmjs.org/

This error happened while installing the dependencies of @atlaskit/editor-common@111.8.12
 at @atlaskit/profilecard@24.32.2
 at @atlaskit/rovo-agent-components@3.23.1
 at atl-react-relay@0.0.0-main-39e79f66

The latest release of relay-runtime is "20.1.1".

Other releases are:
  * dev: 13.0.0-rc.2
  * main: 0.0.0-main-caf20add

If you need the full list of all 3986 published versions run "$ pnpm view relay-runtime versions".

And I can confirm that : pnpm view relay-runtime versions | grep 0.0.0-main-39e79f66 returns nothing.

Are you fetching from somewhere else than npmjs ?!

How come editor-common relies on a branch-build version of relay-runtime instead of a real published version?

We’re very often facing issues with @atlaskit/renderer and @atlaskit/editor-common and often have to end up with dirty hacks and overrides to make this work. Circumventing those issues is taking sometimes a lot of effort and costs a significant development time.

Can this be looked at :folded_hands: :folded_hands: :folded_hands:

3 Likes
2

Think I found the culprit thanks to ChatGPT.

in https://www.npmjs.com/package/@atlaskit/rovo-agent-components/v/3.23.1?activeTab=code

		"react-relay": "npm:atl-react-relay@0.0.0-main-39e79f66"

this is using a specific npm aliasing prefix which doesn’t work with pnpm.

1 Like
3

Is there a viable workaround for resolving this to successfully install? We also have this issue with some @atlaskit components we rely on

4

I can confirm a similar problem on our side. It occurs when both @atlaskit/renderer and @atlaskit/profilecard are used in the same project.