Error on ng add @angular/pwa

[StephenFluin]

Versions

Angular CLI: 6.0.0-rc.6
Node: 9.2.0
OS: linux x64
Angular: 6.0.0-rc.5
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.5.6
@angular-devkit/build-angular     0.5.6
@angular-devkit/build-optimizer   0.5.6
@angular-devkit/core              0.5.6
@angular-devkit/schematics        0.5.8
@angular/cli                      6.0.0-rc.6
@angular/pwa                      0.5.8
@ngtools/json-schema              1.1.0
@ngtools/webpack                  6.0.0-rc.4
@schematics/angular               0.5.8
@schematics/update                0.5.8
rxjs                              6.0.0
typescript                        2.7.2
webpack                           4.5.0

Repro steps

ng new my-app
cd my-app
ng add @angular/pwa

Observed behavior

$ ng add @angular/pwa
Installing packages for tooling via npm.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ @angular/pwa@0.5.8
added 70 packages and removed 4 packages in 6.842s
Installed packages for tooling via npm.
Schematic input does not validate against the Schema: {"help":false,"h":false,"target":"build","configuration":"production"}
Errors:

  Data path "" should have required property 'project'.

Desired behavior

Add PWA super powers to my app

[yankedev]

I have the same-same error with:

Angular CLI: 6.0.0-rc.6
Node: 8.11.1
OS: darwin x64
Angular: 6.0.0-rc.5
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.5.9
@angular-devkit/build-angular     0.5.9
@angular-devkit/build-optimizer   0.5.9
@angular-devkit/core              0.5.9
@angular-devkit/schematics        0.5.8
@angular/cli                      6.0.0-rc.6
@angular/pwa                      0.5.9
@ngtools/json-schema              1.1.0
@ngtools/webpack                  6.0.0-rc.7
@schematics/angular               0.5.8
@schematics/update                0.5.8
rxjs                              6.0.0
typescript                        2.7.2
webpack                           4.6.0

[rfk91]

The following worked for me
ng add @angular/pwa --project myprojectname

[yankedev]

thanks! this fixed my problem :-)

since I'm adding something to an existing project, could --project be optional and take current project as the default?

[cyrilletuzi]

#10486 and angular/devkit#764 should enable this, but both ng add @angular/pwa and ng g service-worker still have their project property set as required in angular/devkit.

I tried to do the PR but I'm not sure there is just to mark project as optional (devkit tests have to explicitly set the project option, so I can't verify it's working without it).

[cyrilletuzi]

PR in angular/devkit#813

[collindutter]

I'm trying to run the command ng add @angular/pwa --project myprojectname and I'm getting the following error: Cannot read property 'options' of undefined. Has anyone else seen this?

[Rumsha001]

@collindutter your angular-cli.json file should be updated to angular.json
Your build options should look like this attachment.

[Rumsha001]

find your correct project name in angular.json file under projects.

[maeri]

@collindutter hey - by any chance any update on this ?

[collindutter]

@maeri yes, actually! In this file on line 137, it iterates over a list of strings, and does some work on them.

['build', 'test'].forEach((target) => {

  const applyTo = architect[target].options;

  if (!applyTo.assets) {
    applyTo.assets = [assetEntry];
  } else {
    applyTo.assets.push(assetEntry);
  }

});

In my angular.json, I had a 'build' section, but I had removed the 'test' section because I didn't need it for my current project. So when it evaluated architect['test'].options it threw the error you're seeing.

Not sure if this is the case for everyone, but it directly fixed it for me. Hope this helps!

[maeri]

@collindutter wow it works !! thank you very much :)