Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
Area
- [ ] devkit
- [ ] schematics
Versions
$ node --version
v8.11.3
$ yarn --version
1.7.0
macOS High Sierra 10.13.5 (17F77)
Repro steps
See https://github.com/mgol/angular-deploy-url-bug.
The log given by the failure
No log but the browser will trigger 404 requests to invalid asset paths from the server-generated CSS. Once the client app loads, all works fine.
Desired functionality
The server should support the deployUrl setting in angular.json and the --deploy-url command line param again as in previous CLI versions.
CLI 6 only supports deployUrl for the browser & devServer targets.
Mention any other details that might be useful
Without --deploy-url support on the server, it's impossible to use consistent asset paths between the server and the client if --deploy-url is used on the client.
Bug Report or Feature Request (mark with an
x)Area
Versions
macOS High Sierra 10.13.5 (17F77)
Repro steps
See https://github.com/mgol/angular-deploy-url-bug.
The log given by the failure
No log but the browser will trigger 404 requests to invalid asset paths from the server-generated CSS. Once the client app loads, all works fine.
Desired functionality
The server should support the
deployUrlsetting inangular.jsonand the--deploy-urlcommand line param again as in previous CLI versions.CLI 6 only supports
deployUrlfor thebrowser&devServertargets.Mention any other details that might be useful
Without
--deploy-urlsupport on the server, it's impossible to use consistent asset paths between the server and the client if--deploy-urlis used on the client.