[rush] Publishing first version to npm

[dbartholomae]

Is this a feature or a bug?

• Feature
• Bug

Please describe the actual behavior.

At the moment when I run rush publish for a package that has not yet been published to npm, I get an error message that a PUT operation cannot be used if there is no existing resource.

What is the expected behavior?

I would expect rush to publish the first version to npm instead of having to do it manually. This additional manual step limits me on how small my packages can be as I don't want to run too much manual stuff when creating a new package.

[javier-garcia-meteologica]

I just successfully published new packages into a private npm registry. First, check that your user account is valid and has the right permissions for the packages that you want to publish in that registry. Second, check that your authToken works.

Then to publish your first package versions, just run this command.

rush publish --publish --include-all

[octogonz]

I suspect the rules are different depending on which registry you are publishing to (NPM, Artifactory, Azure DevOps, GitHub). If someone knows the details, please post them here and we can document them.

Otherwise let's close this issue.

[anilanar]

I can reproduce this but for a package that is already published. For reference, I use a scoped package and I use --set-access-level public. If I use npm publish or yarn publish, it works.

I can only assume that rush publish somehow doesn't respect the auth token in ~/.npmrc or --set-access-level doesn't work.

[anilanar]

I can confirm that rush publish ignores npm auth token from ~/.npmrc. I tried using --npm-auth-token arg and copy/pasted the one in ~/.npmrc and it worked.