Replies: 6 comments 2 replies
-
|
You can publish the new package using a scope (@yourname/warpc) — this usually avoids similar name blocking. |
Beta Was this translation helpful? Give feedback.
-
|
npm has automated checks that prevent publishing a new package if the name is too similar to an existing one, even if the original has been unpublished. This is primarily to prevent typosquatting or confusion. you can do: If it's blocked:
The npm team can manually review and potentially allow the new name, especially if it’s for a legitimate technical rebrand and there’s no intent to mislead users. Avoid extremely similar names: Check availability first: to see if the name is already taken, or to check for conflicts. |
Beta Was this translation helpful? Give feedback.
-
|
npm usually lets you grab any unused name, even if it looks like your old one. So if warpc or wwarpc aren’t taken, you’re good. Just check with npm info and try publishing. No strict “too similar” rule to freak out about. If you hit a wall, hit up npm support or tweak the name a bit. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
I made a package called swarpc -- which stands for "service worker & remote procedure call"
however, i just learned about web workers, and how they're much more appropriate for off-ui-thread computing than SWs, and I kind of have to change the package name.
I can unpublish the package (there aren't any dependents yet), but I'm afraid that I won't be able to publish a new package named warpc or maybe wwarpc because of the "package name too similar" rule.
Is there a way around this? The package naming guidelines are quite vague and don't really answer this question
Beta Was this translation helpful? Give feedback.
All reactions