feat: support npm publish with correct publishConfig#registry in package.json

[JounQin]

close #1271

[changeset-bot]

⚠️ No Changeset found

Latest commit: 303396e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[JounQin]

It seems the current implementation is not enough, in our case, we have @sope:registry=//xxx in project level .npmrc, npm publish --registry is not enough, we'll have to use npm publish --@sope:registry to override, and we need to adapt npm info with correct registry accordingly...

[sambacha]

It seems the current implementation is not enough, in our case, we have @sope:registry=//xxx in project level .npmrc, npm publish --registry is not enough, we'll have to use npm publish --@sope:registry to override, and we need to adapt npm info with correct registry accordingly...

you have to use --"@scope:registry=registryURL", not --registry=registryURL

setting publishConfig in your manifest will override .npmrc

"publishConfig": {
    "@OrgScope:registry": "registry-URL"
  }

[JounQin]

@sambacha Thanks for your advice! Is there any reference of @scope:registry of publishConfig field in package.json?

[JounQin]

npm/cli#7043 (comment)