Replies: 2 comments
-
The 400 error you're encountering when publishing your npm package is typically a bad request error, indicating that something is wrong with the request parameters being sent to the npm registry. The "params" in the error message could be referring to various aspects of your package or your npm configuration. Here are some steps to troubleshoot and resolve this issue: Check Your npm Configuration: |
Beta Was this translation helpful? Give feedback.
-
Hi @Arwa8881 & @Ahmed8881, thanks for being a part of the GitHub Community! While we appreciate you wanting to contribute to Discussions, please note: We made the decision to disable the ability to earn Achievements in our Community in order to discourage users from participating in coordinated or inauthentic activity like rapid questions and answers in order to earn badges. You can learn more about this decision in our announcement post here Achievements will no longer be available in the Community. Note that GitHub's Acceptable Use Policies prohibits coordinated or inauthentic activity like rapid questions and answers. As a result, we'll be unmarking the answer and locking this, and other related posts. Any future violations may result in a temporary or indefinite block from the Community. Thanks for understanding. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
cannot figure out what "params" refers to, it doesn't appear in my source code. The package has never been published before, and does not exist in the registry. I can also publish other packages to the same org without error.
Beta Was this translation helpful? Give feedback.
All reactions