ServiceWorker are not using --deploy-url

[MitkoTschimev]

The service worker is loaded from the base url which is not working if i set a deploy-url

Versions

Angular CLI: 1.6.5
Node: 8.9.4
OS: darwin x64
Angular: 5.2.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker

@angular/cli: 1.6.5
@angular-devkit/build-optimizer: 0.0.42
@angular-devkit/core: 0.0.29
@angular-devkit/schematics: 0.0.52
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.5
@schematics/angular: 0.1.17
typescript: 2.6.2
webpack: 3.10.0

Repro steps

• ng build --deploy-url something/different/than/the/base/url

Observed behavior

Angular uses the base url instead of deploy-url

Desired behavior

The service worker is loaded by following rules:

1. take absolute url if given
2. fallback to deploy-url
3. fallback to base url

[dcarabott]

Experiencing the same issue here. I'm setting a deploy-url on build --prod. The urls are being set correctly in the .html but not in the service worker hash table (ngsw.json). If I manually edit the hash table to include the deploy-url, it works fine.

Angular CLI: 1.7.1
Angular: 5.2.0

[santialbo-actimo]

This is quite an important bug. Can we maybe remove the freq1: low tag so it gets a little more attention and love?

[santialbo-actimo]

For anyone reading this, I managed to get around without too much messing around by re-generating the ngsw.json with the following command

./node_modules/.bin/ngsw-config myDistFolder pathToNgswConfig deployUrl

in my case

./node_modules/.bin/ngsw-config dist/apps/viewer ./ngsw-config.json /viewer

[naveedahmed1]

@santialbo-actimo does your solution work for CDN urls as well? For example if I set deployUrl to https://cdn.mydomain.com/

[gkalpak]

From looking at docs/design/deployurl-basehref.md, it seems that deployUrl is quite inconsistent and baseHref might be a better alternative. There was also a PR to remove it, but it didn't make it for 6.x: angular/devkit#505

I am trying to understand the usecase. Wouldn't --baseHref work for you instead of --deployUrl and if not why?

[MitkoTschimev]

Our cdn is on a different url than the application self.

Example:

https://myapplication.domain.com/ <- index.html is served by a server (configurations are made on the fly)
and the deployments of the resources are on the cdn url
https://cdn.domain.com/.....

Thats the reason why i like the different possibilities for basehref and deploy url

[gkalpak]

So, other than index.html what other files are served from https://myaplication.domain.com/?