Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot publish current packages to the primary npm registry #622

Open
onursumer opened this issue Apr 11, 2024 · 0 comments
Open

Cannot publish current packages to the primary npm registry #622

onursumer opened this issue Apr 11, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@onursumer
Copy link
Collaborator

Current packages are under the @htan scope but we don't own that npm username, so I have created a new organization named ncihtan. We should rename the package scope from @htan to @ncihtan. This will allow us publishing packages under the @ncihtan scope.

See https://docs.npmjs.com/cli/v9/using-npm/scope#publishing-public-scoped-packages-to-the-primary-npm-registry for details about scoped packages.

@onursumer onursumer added the bug Something isn't working label Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant