-
Notifications
You must be signed in to change notification settings - Fork 11.9k
fix(@angular/ssr): enable serving of prerendered pages in the App Engine #28737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
065dcc5
to
27d92dd
Compare
6f56cae
to
f153cd1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few comments, the two main concerns are whether we can simplify the API surface of AngularAppEngine
and how we should let devs interact with the caching policy.
94396da
to
aa236be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I gave some suggestions for the process
, serve
, render
naming, but ultimately I'm happy to defer to you on what you think is best here.
a9ab5e7
to
e640320
Compare
1a6c78b
to
b85f5d9
Compare
b85f5d9
to
3bfec99
Compare
This commit implements the capability for the App Engine to serve prerendered pages directly. Previously, we relied on frameworks like Express for this functionality, which resulted in inconsistent redirects for directories where in some cases a trailing slash was added to the route. **Note:** This change applies only when using the new SSR APIs. When using the `CommonEngine`, a 3rd party static serve middleware is still required.
3bfec99
to
33dac61
Compare
The changes were merged into the following branches: main, 19.0.x |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This commit implements the capability for the App Engine to serve prerendered pages directly. Previously, we relied on frameworks like Express for this functionality, which resulted in inconsistent redirects for directories where in some cases a trailing slash was added to the route.
Note: This change applies only when using the new SSR APIs. When using the
CommonEngine
, a 3rd party static serve middleware is still required.