Create workspace hangs in v8.0.0 due to google analytics prompt

[dopsonbr]

Creating a new nx workspace hangs in v8.0.0 due to google analytics prompt.
Angular console info: version=v8.0.0, type=standalone, os=mac

Expected behavior: A new workspace is successfully created without prompts. Running the create workspace command with npx is successful. npx output:

~/tmp via ⬢ v10.15.3
➜ rm -rf angular-8-test && npx --ignore-existing create-nx-workspace angular-8-test --directory=angular-8-test --collection=@nrwl/workspace --npmScope=usom --no-skipInstall --no-skipGit --no-interactive
npx: installed 53 in 9.331s
Creating a sandbox with Nx...
ng new "angular-8-test" "--directory=angular-8-test" "--collection=@nrwl/workspace" "--npmScope=usom" "--no-skipInstall" "--no-skipGit" "--no-interactive" --collection=@nrwl/workspace
CREATE angular-8-test/README.md (2696 bytes)
CREATE angular-8-test/angular.json (298 bytes)
CREATE angular-8-test/nx.json (195 bytes)
CREATE angular-8-test/tsconfig.json (509 bytes)
CREATE angular-8-test/tslint.json (1574 bytes)
CREATE angular-8-test/.editorconfig (245 bytes)
CREATE angular-8-test/.gitignore (503 bytes)
CREATE angular-8-test/.prettierignore (57 bytes)
CREATE angular-8-test/.prettierrc (26 bytes)
CREATE angular-8-test/package.json (1145 bytes)
CREATE angular-8-test/.vscode/extensions.json (164 bytes)
CREATE angular-8-test/apps/.gitkeep (1 bytes)
CREATE angular-8-test/libs/.gitkeep (0 bytes)
CREATE angular-8-test/tools/tsconfig.tools.json (218 bytes)
CREATE angular-8-test/tools/schematics/.gitkeep (0 bytes)
    Successfully initialized git.

Actual behavior:

new-workspace angular-8-test --directory=angular-8-test --collection=@nrwl/workspace --npmScope=usom --no-skipInstall --no-skipGit --no-interactive

npm init -y
Wrote to /private/var/folders/cg/dk_vx3351vg_2srbw7ktbnzh0000gn/T/tmp-37450RTS65YJkufTm/package.json:

{
  "name": "tmp-37450RTS65YJkufTm",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}


npm install @angular/cli@latest

> @angular/[email protected] postinstall /private/var/folders/cg/dk_vx3351vg_2srbw7ktbnzh0000gn/T/tmp-37450RTS65YJkufTm/node_modules/@angular/cli
> node ./bin/postinstall/script.js

? Would you like to share anonymous usage data with the Angular Team at Google u
nder
Google’s Privacy Policy at https://policies.google.com/privacy? For more details
 and
how to change this setting, see http://angular.io/analytics. (y/N) 

[fdlsistemi]

Same issue here.

[joelmuskwe]

Same Issue too.
Is it possible make the terminal accept input in case if angular cli requires user input for something else in the future.

[Florian3003]

Same issue here.

[clickboxmobile]

Same here.

[alexnoise79]

Console should be editable, is not even possible to copy from it.

[ryanbrear]

Same problem here.

[mapsgeek]

solution would be updating the angular cli from outside angular console, running npm install @angular/cli@latest, then open the console and create the workspace it will work fine

[fdlsistemi]

Not sure about that, mapsgeek.
I had the above-mentioned issue last week on a fresh, brand new install...

Can’t test it right now (currently on vacation): can anyone give it a try?

[mapsgeek]

well i had the same problem few minutes ago and that's what i did and solved it !

[fdlsistemi]

Great, thanks for the confirmation then! =))

[joelmuskwe]

@mapsgeek Thanks it works but this solves the problem but i think the issue is that they assume that angular-console users are using npm for managing packages. For me i was purely using yarn hence the issue was arising till i globally installed @angular/cli in npm. so now i have to manage angular cli versions in both yarn and npm

[mapsgeek]

@joelmuskwe well i think yes they should fix it somehow but at least people can do this for temporary workaround.

[yglin]

Stuck there, too.
From @mapsgeek's solution, Installing latest Angular CLI once, globally also, solves the problem, thanks~

npm install -g @angular/cli@latest

[mrmeku]

Will be fixed in our next release next week

[papirovdavid]

Waiting for fix

[st-clair-clarke]

When will the fix be released?

[emilkoto]

I have been solved it!
Just put in some terminal (and restart angular console):
ng analytics off
Extracted from: https://angular.io/analytics