Anonymous publishing failing for non-scoped package on port other than 4173 #4636
Unanswered
thekevinscott
asked this question in
Q&A
Replies: 2 comments
-
I've also tried with configuration file:
With the same result. Looks like there's something specific about scoped packages vs. non that is resulting in the discrepancies in behaviors. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Initially I had issues, but now it seems to work fine with this configuration.
I don't think it matters what the
Then I just run |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Your Environment
^5.26.1
v16.20.2
pnpm@8.7.0
mac
node
Describe the bug
I cannot publish a non-scoped package anonymously, but I can publish a scoped package anonymously.
To Reproduce
I'm attempting to support anonymous publishing via
pnpm
for local packages. I'm trying to support this in a CI environment, so without the ability to runnpm adduser
.According to this comment a fake token needs to be added to
.npmrc
, e.g.:Which I've added to the
.npmrc
at the root of my monorepo.If I publish a scoped package, i.e.
@bar/baz
, publishing works successfully. However, if I attempt to publish a non-scoped package (foo
), the command fails.The specific command I am running:
This succeeds for
@bar/baz
, but fails forfoo
with:Manually logging in with
npm adduser
resolves the issue, but I can't runnpm adduser
interactively in a CI environment.Expected behavior
I would like to be able to publish all packages anonymously.
Configuration File (cat ~/.config/verdaccio/config.yaml)
I've also tried with
$anonymous
, but since I'm not logged in, I think that$anonymous
and$all
are equivalent. In any case, the end result is the same (foo
fails to publish).Environment information
Beta Was this translation helpful? Give feedback.
All reactions