Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot publish to npm registry for the first time
See original GitHub issueAffected Packages
not sure?
Problem
changeset publish gives me an error like this
it does not 404 on one package that already has an npm registry entry
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Cannot publish to npm registry for the first time #470 - GitHub
Problem. changeset publish gives me an error like this. image. it does not 404 on one package that already has an npm registry...
Read more >I cannot publish to npm - node.js - Stack Overflow
I'm trying to publish a package for the first time, sorry in case I missed out anything obvious. Thank You for reading. node.js...
Read more >How to Publish Your First npm Package | by Bret Cameron
Once you're up-and-running, publishing an npm package can be as easy as typing npm publish into the terminal. But setting up your package ......
Read more >npm-publish - npm Docs
Description. Publishes a package to the registry so that it can be installed by name. By default npm will publish to the public...
Read more >How to make your npm package available to the public for the ...
This is a summary of the steps to release the npm package to the public npm registry for the first time.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
https://github.com/relay-tools/relay-graphql-js/blob/main/.changeset/config.json here’s the config fwiw!
I will assume that the issue could been related to the fact that the organization on npm could have been created after trying to publish packages. If the issue was not that and if the issue persists - please let us know, I can reopen this ticket if we get more info on the subject.