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
Now, I am not using ng deploy or firebase deploy since they require @angular-devkit/build-angular and the SSR function being deployed is not working. Instead, I created a separate Firebase Repo and initialised both hosting and functions.
In the Firebase Repo, I am successfully deploying both hosting and functions using firebase deploy. The SSR function works, save for paths redirected to the ErrorComponent:
src/app/app.routes.ts
{
path: "**",
redirectTo: "/error",
},
When seeing the Google Cloud Console logs for the Cloud function, the express instance is giving a 302 response (which is what you'd expect from a redirect), however, instead of staying on port 80, the redirect URL is given on port 8080, which is the internal port being using by the express instance. I reckon that server.ts needs to be modified, however, I don't know how.
The text was updated successfully, but these errors were encountered:
I am using @angular/[email protected], and I have the following:
src/server.ts
src/app/app.routes.ts
src/app/app.routes.server.ts
src/app/app.config.ts
src/app/app.config.server.ts
Now, I am not using
ng deploy
orfirebase deploy
since they require@angular-devkit/build-angular
and the SSR function being deployed is not working. Instead, I created a separate Firebase Repo and initialised both hosting and functions.firebase.json
functions/ssr/index.js
In the Firebase Repo, I am successfully deploying both hosting and functions using
firebase deploy
. The SSR function works, save for paths redirected to the ErrorComponent:src/app/app.routes.ts
When seeing the Google Cloud Console logs for the Cloud function, the express instance is giving a 302 response (which is what you'd expect from a redirect), however, instead of staying on port 80, the redirect URL is given on port 8080, which is the internal port being using by the express instance. I reckon that server.ts needs to be modified, however, I don't know how.
The text was updated successfully, but these errors were encountered: