How to use both @zitadel/zitadel-node and @zitadel/react in the same repo?

Hello!

Npm doesn't allow specifying registries on a repo level, only per scope. How am I supposed to install both

@zitadel/zitadel-node

@zitadel/zitadel-node

@zitadel/zitadel-node

@zitadel/zitadel-node and

@zitadel/react

@zitadel/react

@zitadel/react

@zitadel/react in the same repository?

This works for getting

@zitadel/zitadel-node

@zitadel/zitadel-node

@zitadel/zitadel-node

@zitadel/zitadel-node installed, but breaks installation of

@zitadel/react

@zitadel/react

@zitadel/react

@zitadel/react

@zitadel:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}

@zitadel:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}

@zitadel:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}

@zitadel:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}

Would you consider publishing all packages to the same place?

Thanks

Ask Inkeep•12/3/25, 6:11 AM

Hi @bazze, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.

Ask Inkeep•12/3/25, 6:11 AM

Answer

Based on the available sources, there's a registry configuration difference between the two packages:

@zitadel/zitadel-node

@zitadel/zitadel-node

is published on GitHub Packages and requires this

.npmrc

.npmrc

configuration (1) :

@zitadel:registry=<https://npm.pkg.github.com>

@zitadel:registry=<https://npm.pkg.github.com>

@zitadel/react

@zitadel/react

is published on the public npm registry and can be installed with (2) :

yarn add @zitadel/react

yarn add @zitadel/react

The issue you're experiencing occurs because setting @zitadel:registry=<https://npm.pkg.github.com%60> redirects **all** @zitadel:registry=<https://npm.pkg.github.com%60> redirects **all** @zitadel scoped packages to GitHub Packages, but scoped packages to GitHub Packages, but @zitadel/react

 isn't available there.

**Workaround:**

Unfortunately, the available sources don't provide a direct solution for using both packages simultaneously with npm's scope-level registry configuration. This appears to be a limitation of how the packages are currently distributed across different registries.

I'd recommend clicking the "Ask for help" button to tag a team member who can provide guidance on:
- Whether there are plans to publish all

 isn't available there.

**Workaround:**

Unfortunately, the available sources don't provide a direct solution for using both packages simultaneously with npm's scope-level registry configuration. This appears to be a limitation of how the packages are currently distributed across different registries.

I'd recommend clicking the "Ask for help" button to tag a team member who can provide guidance on:
- Whether there are plans to publish all

@zitadel` packages to the same registry

Alternative installation methods for using both packages together

Ask Inkeep•12/3/25, 6:11 AM

To learn more, see the sources I considered:

[1] Node.js Client
[2] ZITADEL with React

Ask Inkeep•12/3/25, 6:11 AM

Feel free to tag @Ask Inkeep with additional questions.

AAsk Inkeep To learn more, see the sources I considered: [[1] Node.js Client](https://zit...

Ask InkeepAPP•12/3/25, 6:11 AM

Got it. Tagging @Rajat for additional help.

Rajat•12/4/25, 1:51 PM

hey @bazze thanks for your question, I have raised it internally and I will get back to you on this, Thanks