How to publish a package with a dependenciy under another registry

[labbbirder]

I'm publishing my package under a workspace with package.json like this:

{
  "name": "com.bbbirder.pkg-in-workspace",
  "version": "0.0.43",
  "dependencies": {
    "com.bbbirder.another-local-package": "1.0.3",
    "com.another-registry.remote-package": "1.10.1"
  }
}

As u can see abow, the dependency com.another-registry.remote-package was not on neither npmjs or my own registry, it was kept by a thirt-party registry.

When I execute lerna publish, the following error occurs:

lerna ERR! Error: Command failed with exit code 1: npm install --package-lock-only --ignore-scripts
lerna ERR! npm ERR! code ETARGET
lerna ERR! npm ERR! notarget No matching version found for com.another-registry.remote-package@1.10.1.
lerna ERR! npm ERR! notarget In most cases you or one of your dependencies are requesting
lerna ERR! npm ERR! notarget a package version that doesn't exist.
lerna ERR!

So, is there a way to let lerna recognize thirty-party(not the npmjs.org) dependency, or mark the dependency as remote, or just skip the dependenting check?

Thx

[labbbirder]

Uh yeah, I found a resolution then.
I clone the remote package into my workspace, and ignore it in git.
and then everything works well.

[fahslaj]

Hi @labbbirder, you can configure different registries to use for different package scopes. If your packages in the other remote registry follow a consistent unique scope pattern, then the npm install shouldn't fail. See the npm scope docs for details on how to configure this.

[labbbirder]

Hi @fahslaj , thank for your reply. The great suggestion helps a lot.