Issue Publishing Scoped Package to npm Registry

[mohammed786]

Select Topic Area

Question

Body

I am trying to publish a package under the @LoginRadius scope from a private GitHub repository located at https://github.com/LoginRadius
.

However, while publishing, I encountered the following error:

npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm error code E404
npm error 404 Not Found - PUT https://registry.npmjs.org/@loginradius%2flr-core-js - Not found
npm error 404
npm error 404  '@loginradius/lr-core-js@1.0.0' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-09-19T09_25_06_732Z-debug-0.log
Error: Process completed with exit code 1.

Could you please help me understand why this error is occurring and guide me on how to successfully publish this package under the @LoginRadius scope?

Thank you for your assistance.

[jfullstackdev]

as for me, the possible causes are :

1. Scope Ownership / Org Membership
   If you try to publish under @LoginRadius, you must have the right permissions in the LoginRadius organization on npm. Maybe you’re not a member, or don't have publishing rights.

   https://stackoverflow.com/questions/39115101/getting-404-when-attempting-to-publish-new-package-to-npm

2. you must be logged in correctly
   If your npm credentials (token, login) are wrong or missing, npm will return “404 Not Found” rather than “permissions” in some cases. Calling npm login or using a valid token is required. ( same link reference in no. 1 )

3. Two-Factor Authentication (2FA)
   If the org requires 2FA, then publishing might fail if your user doesn’t have 2FA or your token isn’t allowed under those constraints.

4. Package Name collisions or Registry Misconfig
   Maybe the package name is already taken under that scope (by someone else), or there is something wrong with package.json fields (name, version).

5. publishConfig or .npmrc Misconfig
   If your project has a .npmrc that points to a different registry, or your publishConfig.registry is wrong, or your token is scoped incorrectly.

6. you don’t have an Org on npm
   To use a scoped package like @LoginRadius/..., the npm account or the group must exist. If @LoginRadius is not registered or created as an org in npm, then npm doesn’t know how to handle that scope.

---

possible things you can do :

1. confirm that @LoginRadius is an existing Org on npm

   • Visit npmjs.com and check that the org LoginRadius exists.
   • If not, someone in your team must create it.

2. check that the user (mohammed786) is added as a member with Publish Rights

   • Org membership settings → make sure you have “maintainer” or a role that has publishing privileges.

3. login to npm

   • Run npm login and ensure you’re using correct credentials with access to the org.
   • If using CI, ensure the token used has publish permission under the org.

4. check package.json: name field

   {
     "name": "@loginradius/lr-core-js",
     "version": "1.0.0",
     // other fields ...
   }

   Make sure the name matches the scope and desired package name exactly.

5. set the Access Level
   Use npm publish --access public (if you want it public). For scoped packages, default might be restricted.

6. check for an Existing Package or Name Conflict
   Perhaps someone else claimed @loginradius/lr-core-js but removed it or something weird. Use npm view @loginradius/lr-core-js to see if anything exists.

7. review .npmrc or publishConfig

   • If .npmrc in project has wrong registry.
   • If using GitHub Actions / CI, ensure NPM_TOKEN is set correctly and not expired.

8. verify email Verification
   Sometimes npm blocks publishing if your email isn’t verified.

[jeremylanger]

Just ran into this myself while upgrading to Trusted Providers and OIDC. My issue ended up being my Github Action wasn't using the latest npm version (must be at least 11.5.1). If you're in the same situation, just put this before you run your npm ci and npm publish:

# Ensure npm 11.5.1 or later for trusted publishing
- run: npm install -g npm@latest