Path to ngsw-config.json

[zygimantas]

Versions

Angular CLI: 6.0.0
Node: 10.0.0
OS: win32 x64
Angular: 6.0.0
... cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.6.0
@angular-devkit/build-optimizer   0.6.0
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@ngtools/webpack                  6.0.0
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

Observed behavior

ngsw-config.json must be in src/ directory

Desired behavior

There may be multiple apps configured in angular.json, so the path ngsw-config.json should be configurable also; ngsw-config.json should not be shared across different apps; file name should be configurable;

[menosprezzi]

I suggest also a custom path to ngsw-config.json as we see in other config files in angular.json

[mackelito]

Correct me if I'm wrong but if we run 'ng add @angular/pwa --project project-name' the ngsw-config is added to root '/' right?

[alan-agius4]

There is already an option to specify the ngsw config path location. This is called ngswConfigPath which can also be specified in the build options https://angular.io/cli/build

That said, maybe we should generate ngsw-config.json under the project sourceRoot if root is empty similar to the karma.conf.js

Proposed:

-- src
---- ngsw-config.json
-- project
---- app
------ ngsw-config.json

Current:

-- ngsw-config.json
-- src
-- project
---- app
------ ngsw-config.json

@clydin, @filipesilva, what do you reckon?

[filipesilva]

@alan-agius4 yes, I agree it should be like your proposal. Similar config files are also under src/.

[angular-automatic-lock-bot]

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.}