Complete Guide to Removing Packages in Angular CLI: From ng add to npm uninstall

Overview of Package Management in Angular CLI

In modern Angular development, package management is a core aspect of project maintenance. Angular CLI provides a powerful toolchain to streamline development workflows, with the ng add command introduced in Angular 6 bringing new dimensions to package installation.

The Uniqueness of ng add Command

Unlike the traditional npm install <package> command, ng add does more than just download dependencies through the package manager. It executes an installation script (implemented as a schematic) that can:

• Update project configuration
• Add additional dependencies (e.g., polyfills)
• Scaffold package-specific initialization code

This intelligent installation approach makes ng add a more comprehensive package integration tool rather than just a simple dependency downloader.

Current State of Package Removal

Despite the powerful package installation capabilities of ng add, Angular CLI currently lacks a corresponding removal command. Executing ng help confirms that no built-in commands like ng remove or ng delete exist in current versions. This means developers cannot directly use Angular CLI to completely undo all actions performed by ng add.

Correct Approach Using npm uninstall

At the current stage, the standard method for removing packages is using npm's uninstall command:

npm uninstall <package-name>

This command performs the following operations:

• Completely removes package files from the node_modules directory
• Deletes package references from dependency objects in package.json
• Automatically updates package-lock.json or npm-shrinkwrap.json files

Detailed Working Mechanism of npm uninstall

The npm uninstall command offers flexible removal options:

Default Behavior

By default, the command removes packages from both node_modules and package.json:

npm uninstall lodash

This completely cleans up all installation content related to the lodash package.

Preserving package.json References

If you only need to remove a package from node_modules without affecting package.json, use:

npm uninstall --no-save lodash

This is particularly useful in certain debugging scenarios.

Forcing Save Changes

When save=false is set in npm configuration, use the --save or -S flag to ensure package removal from package.json:

npm uninstall --save lodash

Verifying Uninstallation Operations

To ensure successful package removal, verify using the following methods:

On Unix systems (such as macOS):

ls node_modules

On Windows systems:

dir node_modules

Check the output to confirm that the target package directory no longer exists.

Handling Global Packages

For globally installed packages, the removal command requires the -g flag:

npm uninstall -g <package-name>

For example, to remove globally installed jshint:

npm uninstall -g jshint

Practical Application Example

Suppose we previously installed Angular Material using ng add @angular/material and now need to remove it:

npm uninstall @angular/material

This command will:

• Remove the node_modules/@angular/material directory
• Delete @angular/material from dependencies in package.json
• Update package-lock.json

Considerations and Best Practices

When using npm uninstall, note the following:

• Some configuration changes made by ng add may require manual restoration
• It's recommended to backup important configuration files before removing packages
• Check if other packages depend on the package being removed
• Run npm audit to ensure no security vulnerabilities are introduced

Future Outlook

Although Angular CLI currently lacks native package removal commands, the community continues to discuss the possibility of adding ng remove functionality. Future versions may provide more complete package lifecycle management tools capable of intelligently undoing all changes made by ng add.

Conclusion

In the current Angular development environment, while ng add provides powerful package installation capabilities, package removal still relies on traditional npm toolchain. By correctly using the npm uninstall command, developers can effectively manage project dependencies, maintaining clean and maintainable codebases. Understanding how these tools work and their limitations is crucial for building robust Angular applications.