How to delete an npm package from the npm registry?

In practice, for various reasons, npm does not encourage users to remove published packages from the npm registry. This is because if a package is widely used, removing it can cause a chain reaction for other projects depending on it, potentially leading to build or runtime errors. However, if you must remove the package, you can follow these steps:

1. Log in to your npm account: First, ensure npm is installed and use the command-line tool to log in to your npm account. You can use the following command to log in:

   bash
   npm login

   Enter your username, password, and email address to complete the login.

2. Confirm the package name and version: You need to know the exact package name and the version you want to remove. If you want to remove a specific version, you must specify the version number. You can use the following command to view all versions of the package:

   bash
   npm view <package_name> versions

3. Remove the package or a specific version:

   • If you need to remove the entire package (including all versions), use:

     bash
     npm unpublish <package_name> --force

   • If you only need to remove a specific version, use:

     bash
     npm unpublish <package_name>@<version>

4. Important considerations:

   • npm allows package removal within 72 hours of publication by default. After this window, npm requires special justification to remove the package.
   • For widely used packages, consider releasing a new version to resolve the issue instead of directly removing the package.

Example: Suppose I previously published an npm package named example-package, and later discovered that version 1.0.1 has serious issues that need to be removed. First, ensure you are logged in using npm login, then use the following command to remove this specific version:

bash
npm unpublish example-package@1.0.1

This way, only version 1.0.1 is removed, while other versions remain available, minimizing the impact on users depending on your package.

In summary, when deciding to remove a package from the npm registry, carefully consider its impact on the community and seek alternative solutions whenever possible.