x)- [x] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
No
After installing the latest CLI beta ( 8.0.0-beta.10) , you get the prompt about analytics.
If answering no, the assumption would be to not get asked when creating a new project later.
At least not when running ng new ... --defaults or ng new ... --no-interactive.
ng analytics off
ng new cli-analytics --default --no-interactive
# still get the analytics prompt
I'd like to second this. The prompt also causes an issue when trying to run npm ci on a CI server, it halts the installation process with a prompt.
I was able to work around by using yes | npm ci || true but that leaves a lot to be desired from a major package like Angular - given a lot of people are likely to run into the same issue.
I think it's the same issue, but Circle CI is still broken with Angular CLI beta.16, due to the analytics prompt (which should not happen in non-interactive mode). Install is done with a classic npm install.
This breaks any CI install by asking for analytics permissions on CI and blocking completion of npm install. It is before the CLI is even ready to run locally. I believe the prompt should not run on NPM install, but rather on first use of an ng command. with the exception of ng analytics so a CI could disable it.
As a travis-ci workaround I added the environment variable: NG_CLI_ANALYTICS=ci
as described here: https://github.com/angular/angular-cli/blob/f8fe4b0ee82d880396119a2594f3cee8dadb2947/docs/design/analytics.md#ci
One other note to the cli team: in the cli output with the analytics prompt, the link for more info provided is https://angular.io/analytics but that 404's.
Right now, prolly b/c its still a beta, it is on: https://next.angular.io/analytics
Original issue was resolved in the referenced PR. CI related issues with project level analytics options are being tracked in #14265.
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
_This action has been performed automatically by a bot._
Most helpful comment
I'd like to second this. The prompt also causes an issue when trying to run
npm cion a CI server, it halts the installation process with a prompt.I was able to work around by using
yes | npm ci || truebut that leaves a lot to be desired from a major package like Angular - given a lot of people are likely to run into the same issue.