Angular · Senior · Question 57 of 75

When is `ngSkipHydration` on a component a reasonable workaround?

✓Correct answer: When a component manipulates the DOM directly (e.g. a third-party widget) and can't be fixed yet - it's re-rendered on the client instead
2To speed up hydration of every component
3To disable SSR for the whole app

Explanation

Skipping hydration loses its benefits for that subtree and can cause a flash. Prefer fixing direct DOM manipulation by using Angular APIs.

Further reading

Angular: Hydration ↗

Test yourself

Take the Angular · Senior quiz: questions and options are shuffled, and you get a review of your mistakes at the end.