You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2022. It is now read-only.
Which causes wrong assets path in css on the universal generated response.
Where as when doing a browser build the baseHref is properly appended in postCss processing as expected.
baseHref set to "https://cdn.example.com"
.icon {
background: url('/assets/icon.svg') no-repeat center center;
}
angular-devkit/build-angular:browser-> postCss ->
.icon {
background: url('https://cdn.example.com/assets/icon.svg') no-repeat center center;
}
angular-devkit/build-angular:server -> postCss -> no change which leads to wrong URL in first initial server rendered response in combination to html base href tag
Desired functionality
The postcss step in server build should append the path with baseUrl or deployUrl as in browserBuild
so that the initial response generated by universal has correct path to assets if relative URL is used
The text was updated successfully, but these errors were encountered:
Bug Report or Feature Request (mark with an
x
)Area
Versions
angular-devkit/architect 0.6.5
Repro steps
Cannot pass baseHref or deployUrl option when running
ng run web:server:production
which contains
Which causes wrong assets path in css on the universal generated response.
Where as when doing a browser build the baseHref is properly appended in postCss processing as expected.
baseHref set to "https://cdn.example.com"
angular-devkit/build-angular:browser-> postCss ->
angular-devkit/build-angular:server -> postCss -> no change which leads to wrong URL in first initial server rendered response in combination to html base href tag
Desired functionality
The postcss step in server build should append the path with baseUrl or deployUrl as in browserBuild
so that the initial response generated by universal has correct path to assets if relative URL is used
The text was updated successfully, but these errors were encountered: