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
Avoid having to put the client bootstrap in DOMContentLoaded for TransferState to work properly #20484
Comments
@vikerman do you suggest doing something like this?
|
Updates TransferState documentation to make note of angular/angular issue angular#20484 and the fact that `BrowserTransferStateModule` requires changing a typical Angular app's bootstrap process in order to work properly.
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends. Find more details about Angular's feature request process in our documentation. |
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage. We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package. You can find more details about the feature request process in our documentation. |
Thanks this made us to understand why a critical bug happens just some times. I agree this should be part of angular function but anyway is good that there is a easy fix for it. |
The script tag that loads the main.js file can be deferred using the |
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. |
Currently the client of a SSR Angular app needs to wait for DOMContentLoaded to complete before bootstrapping so that TransferState can reliably get the contents of the transferred state from the DOM.
Need to investigate whether we can handle this more transparently without the user needing to bootstrap in a specific way on the client side.
The text was updated successfully, but these errors were encountered: