ng-analytics

Enable analytics for the current project

$ ng analytics [[on|enable]]

$ ng analytics [[on|enable]] [[-g|--global]]

$ ng analytics [[off|disable]]

$ ng analytics [[off|disable]] [[-g|--global]]

$ ng analytics info

$ ng analytics prompt

ng analytics [on|off]

on
    Enables Angular CLI analytics sharing

off
    Disables Angular CLI analytics sharing

--help, -h
    Displays help for the command

--verbose
    Enables verbose logging (global ng option)

The ng analytics command configures whether the Angular CLI shares anonymous usage data with the Angular team via Google Analytics. This helps improve the CLI by tracking common commands, errors, and features used.

By default, analytics is disabled to respect user privacy. Running ng analytics without arguments displays the current status (enabled or disabled). Use on to opt-in, sending data like command invocations, project sizes, and dependency versions. Data is anonymized—no personal info, IPs, or project names are collected.

This feature was added to gather insights ethically. Opting in contributes to Angular's development; opting out ensures no data sharing. Changes are stored in the global Angular CLI configuration file (~/.angular-cli.json or similar).

Note: Requires Node.js/npm and Angular CLI installation via npm install -g @angular/cli. Analytics transmission occurs on CLI usage, not affecting app builds.

Analytics data sent only if enabled and internet available. No data collected on opt-out. Global config overrides local; check with ng config cli.analytics. Not available in all CLI versions pre-v6.

Run ng analytics alone to view current status: Analytics: false or true.

Set via config: ng config cli.analytics true or false.

Introduced in Angular CLI v6 (May 2018) amid privacy concerns, replacing implicit tracking. Evolved with CLI updates; v12+ refined data collection for better insights while maintaining opt-in model.

ng(1), ng config(1), npm(1)