Package not being added to yarnpkg.com registry (but fine on NPM registry) about website

[hv-pul]

For some reason it is published as private 🤦
Sorry for the troubles

[hv-pul]

Some more info:

Strangely local installs work for me, but not for my coworkers. I have not linked the package or anything. My yarn.lock contains this entry:

"@hv/flying-focus@^0.0.6":
  version "0.0.6"
  resolved "https://registry.yarnpkg.com/@hv/flying-focus/-/flying-focus-0.0.6.tgz#7b235d181b883fc4bfba89377f75d9f185114128"
  integrity sha512-OOwfbYHavMslnEjZvWu9WUvu/uuzmcYZF5ksP/RC9otTnou4rsyc4YJpe50+0eTPxpAk59/fD1KTxKllPlYBng==

Opening https://registry.yarnpkg.com/@hv/flying-focus/-/flying-focus-0.0.6 gives me this though:

{"code":"ResourceNotFound","message":"/@hv/flying-focus/-/flying-focus-0.0.6 does not exist"}

Opening https://registry.yarnpkg.com/@hv/flying-focus/-/flying-focus-0.0.6.tgz#7b235d181b883fc4bfba89377f75d9f185114128:

{"error":"Not found"}

My bitbucket build job also fails with this error:

error An unexpected error occurred: "[https://registry.yarnpkg.com/@hv/flying-focus/-/flying-focus-0.0.6.tgz:](https://registry.yarnpkg.com/@hv/flying-focus/-/flying-focus-0.0.6.tgz) Request failed \"404 Not Found\"".

And here is my config info:

yarn config v1.22.17
info yarn config
{
  'version-tag-prefix': 'v',
  'version-git-tag': true,
  'version-commit-hooks': true,
  'version-git-sign': false,
  'version-git-message': 'v%s',
  'init-version': '1.0.0',
  'init-license': 'MIT',
  'save-prefix': '^',
  'bin-links': true,
  'ignore-scripts': false,
  'ignore-optional': false,
  registry: 'https://registry.yarnpkg.com',
  'strict-ssl': true,
  'user-agent': 'yarn/1.22.17 npm/? node/v16.13.1 darwin arm64',
  email: REMOVED EMAIL,
  lastUpdateCheck: 1643820476011,
  username: 'hv-pul'
}
info npm config
{
  'REMOVED Private registry info',
  'REMOVED Private registry info',
  'REMOVED Private registry info',
  'REMOVED Private registry info',
  'REMOVED Private registry info',
  'REMOVED Private registry info',
  '//registry.npmjs.org/:_authToken': 'REMOVED TOKEN',
  'link-workspace-packages': true
}
✨  Done in 0.01s.

[Haroenv]

The package is private, and thus doesn't show up in the yarn website, as it doesn't (yet, although I don't think it's really possible with npm apis) use login information to show private packages.

Trying to access packages via url without authorisation headers indeed looks the same as if the package didn't exist.

I'm assuming your colleagues either haven't correctly logged in on their terminal or don't actually have access for their account to the hv organisation.

As this isn't an issue for the yarn website, but for npm support probably, I'll close this issue for now.

Good luck!

[Haroenv]

No problem! Scoped packages are indeed published as private by default, unless you specify --access public while publishing