angular-cli: ng new 'Data path "" should NOT have additional properties(dryRun).'

Versions

Angular CLI: 6.0.4
Node: 9.11.1
OS: win32 x64
Angular:
...

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.6.4
@angular-devkit/core         0.6.4
@angular-devkit/schematics   0.6.4
@schematics/angular          0.6.4
@schematics/update           0.6.4
rxjs                         6.2.0
typescript                   2.7.2

Repro steps

ng new <app name>

Observed behavior

ng new vui
Schematic input does not validate against the Schema: {"dryRun":false,"version":"6.0.4","skipGit":false,"skipInstall":false,"linkCli":false,"commit":true,"newProjectRoot":"projects","inlineStyle":false,"inlineTemplate":false,"routing":false,"prefix":"app","style":"css","skipTests":false}
Errors:

  Data path "" should NOT have additional properties(dryRun).

Desired behavior

pretty obvious

Mention any other details that might be useful (optional)

Fresh install of the CLI on Windows 10 using Powershell - let me know if this is not supported?

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 26
Comments: 33 (1 by maintainers)

Links to this issue

A broken version of the Angular CLI was released last night

Most upvoted comments

looks like the issue is with Angular CLI: 6.0.4

downgrade to 6.0.3 and ng new works for me now

npm uninstall -g @angular/cli npm cache verify npm install -g @angular/cli @6.0.3

## but when I run “ng g c header” i get

Schematic input does not validate against the Schema: {"dryRun":false,"inlineStyle":false,"inlineTemplate":false,"changeDetection":"Default","styleext":"css","spec":true,"flat":false,"skipImport":false,"export":false}
Errors:

  Data path "" should NOT have additional properties(dryRun).

this just started happening

UPDATE (workaround)

in your package.json look for “@angular/compiler-cli”: “^6.0.2”

this will install the 6.0.4 which was updated today about 2 hours ago and thats where the issues from from.

workaround

change this “@angular/compiler-cli”: “^6.0.2” to this “@angular/compiler-cli”: “6.0.3”

this will force it to use 6.0.3

delete your package-lock.json and the node_moudles folder then run “npm install”

— make sure you are using CLI 6.0.3 ---- the latest is 6.0.4 and it will not work with this

+12

eliteproxy7 on May 25, 2018

This issue has been addressed in 2 ways…

Version 6.0.5 was released, which is the same as version 6.0.3
A PR was merged to be included in a future release to resolve this issue in the future #11015

Apologies for any issues this may have caused.

Brocco on May 25, 2018

“Fixed” as in they re-release 6.0.3 with a version bump.

ashleybroughton on May 25, 2018

Looks like the new 6.0.5 version fixes, thanks @hansl !

moltenkaizen on May 25, 2018

Can confirm: npm install -g @angular/cli@6.0.3 works

ryanzmann on May 25, 2018

This might not be best practice, but adding the dryRun property to the schema will let you run on the latest version without this problem.

%appdata%\npm\node_modules\@angular\cli\node_modules\@schematics\angular\ng-new\schema.json

  "properties": {
    "dryRun": {
      "description": "Dryrun",
      "type": "boolean",
      "default": false
    },

ashleybroughton on May 25, 2018

Great time to upgrade the CLI haha will try 6.0.3 thanks

pbuhrmann on May 25, 2018

Confirmed downgrading to 6.0.3 resolves the issue, it was introduced in 6.0.4.

Edit: confirmed the above issue. Looks like ng g doesn’t work for 6.0.3 or 6.0.2.

ghost on May 25, 2018