Title: Hydration: add a warning when ApplicationRef.isStable doesn't emit `true` after some time · Issue #50285 · angular/angular · GitHub
Open Graph Title: Hydration: add a warning when ApplicationRef.isStable doesn't emit `true` after some time · Issue #50285 · angular/angular
X Title: Hydration: add a warning when ApplicationRef.isStable doesn't emit `true` after some time · Issue #50285 · angular/angular
Description: Which @angular/* package(s) are relevant/related to the feature request? core Description Currently, Angular hydration logic depends on the ApplicationRef.isStable on the client for a couple things: when the post-hydration DOM cleanup sh...
Open Graph Description: Which @angular/* package(s) are relevant/related to the feature request? core Description Currently, Angular hydration logic depends on the ApplicationRef.isStable on the client for a couple things...
X Description: Which @angular/* package(s) are relevant/related to the feature request? core Description Currently, Angular hydration logic depends on the ApplicationRef.isStable on the client for a couple things...
Opengraph URL: https://github.com/angular/angular/issues/50285
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Hydration: add a warning when ApplicationRef.isStable doesn't emit `true` after some time","articleBody":"### Which @angular/* package(s) are relevant/related to the feature request?\r\n\r\ncore\r\n\r\n### Description\r\n\r\nCurrently, Angular hydration logic depends on the `ApplicationRef.isStable` on the client for a couple things:\r\n\r\n- when the post-hydration DOM cleanup should happen (to remove all unclaimed DOM segments)\r\n- when to output hydration stats into a console\r\n- when the HttpClient cache should no longer be in use\r\n\r\nWe've received a few requests where hydration stats are not displayed in a console after hydration and in all cases this leads into `ApplicationRef.isStable` not emitting `true`. There are various reasons for this and in in vast majority of cases the problems are **unrelated** to hydration. However, previously this was not \"visible\" in the app, but with hydration the use of `ApplicationRef.isStable` increased and it becomes more important to get to the \"stable\" state.\r\n\r\nAs a first step to improve the DX, we should add a warning when the app didn't get to the \"stable\" state after some time (N seconds, N=10?). For this warning it'd be also important to have an error guide page to explain this problem in more details and provide some hints on how to resolve that. We could also use this error guide page to collect more information about use-cases over time.\r\n\r\nRelevant code: https://github.com/angular/angular/blob/main/packages/core/src/hydration/api.ts#L162-L183.","author":{"url":"https://github.com/AndrewKushnir","@type":"Person","name":"AndrewKushnir"},"datePublished":"2023-05-14T00:32:25Z","url":"https://github.com/angular/angular/issues/50285"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:9a017945-8c07-b8b8-f1d0-cc572b7ceb05 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D2E4:A71F9:E18FB5:11BAFAB:6B013FCA |
| html-safe-nonce | a57ef543561a302a74d3cf922f09a5b6c735a1a84451748c1832c21921d54651 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEMkU0OkE3MUY5OkUxOEZCNToxMUJBRkFCOjZCMDEzRkNBIiwidmlzaXRvcl9pZCI6IjI1NTQ0MDcxNDM2ODM5OTc2NDIiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | c18139cc54de2eff748aa3593ef94f17c38d3305f487ac675edecfaae84cf5b1 |
| hovercard-subject-tag | issue:1708776526 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/50285/issue_layout |
| twitter:image | https://opengraph.githubassets.com/3b9b3e5925640a7bd2fb32b14d9720d7201be15305966e018b0db8d7be5d2f20/angular/angular/issues/50285 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/3b9b3e5925640a7bd2fb32b14d9720d7201be15305966e018b0db8d7be5d2f20/angular/angular/issues/50285 |
| og:image:alt | Which @angular/* package(s) are relevant/related to the feature request? core Description Currently, Angular hydration logic depends on the ApplicationRef.isStable on the client for a couple things... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | AndrewKushnir |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular git https://github.com/angular/angular.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 24195339 |
| octolytics-dimension-repository_nwo | angular/angular |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 24195339 |
| octolytics-dimension-repository_network_root_nwo | angular/angular |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | canary-2 |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width