Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteAngular error NG05000 means hydration is enabled while the app uses a custom or no-op Zone.js implementation that Angular does not fully support. Start by checking the project’s Zone.js setup and hydration configuration. If you need a custom zone, verify that it reports stability at the right time; the warning does not, by itself, prove that the server-rendered DOM has a mismatch.
What NG05000 means
Angular’s NG05000 documentation identifies a configuration in which hydration is used with a custom or no-op Zone.js instance. Angular describes it as “not yet a fully supported configuration.” The documentation does not specify an affected Angular or Zone.js version range, nor does it promise a universal code change that resolves the warning.
As an Amazon Associate I earn from qualifying purchases.
Hydration restores a server-rendered Angular application in the browser by reusing the rendered DOM and application state. Zone.js provides a stability signal that Angular uses to time work such as server-side serialization and browser-side cleanup of DOM nodes that were not claimed during hydration. A custom implementation can change when that signal arrives. If it arrives too early or too late, Angular may perform that work at the wrong time.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to investigate and address the warning
-
Check the Zone.js setup
Inspect the application’s Zone.js configuration and determine whether it intentionally uses a custom or no-op implementation. Review the project’s hydration configuration as well; Angular’s hydration guide describes the hydration lifecycle and setup.
-
Use a supported arrangement where possible
If the custom or no-op zone is not required, use a Zone.js arrangement supported by the application’s Angular configuration. Confirm the installed Angular and Zone.js versions and consult the documentation for those releases before changing dependencies: the NG05000 guidance does not name a version range or identify a release that fixes the warning.
-
Verify custom stability reporting
If the application must keep its custom implementation, inspect when its
onStableevent is emitted. Check that it reflects the point when the relevant work has actually settled, and test hydration behavior in both the server-rendering and browser phases. Angular’s documentation gives no universal event timing value, so timing needs to be validated against the application’s work rather than copied as a fixed setting.Rank #2
NG05000 versus NG0506
These warnings identify different conditions. NG05000 concerns an unsupported Zone.js implementation used with hydration. NG0506 concerns a browser application that remains unstable: Angular documents it when ApplicationRef.isStable does not emit true within 10 seconds during hydration. Pending microtasks or macrotasks can contribute to that delay. See Angular’s NG0506 documentation.
Recommended Free Tools
| Warning | What it identifies | Diagnostic focus |
|---|---|---|
| NG05000 | Hydration used with a custom or no-op Zone.js implementation that is not fully supported. | Inspect the zone setup and when its onStable event fires. |
| NG0506 | The browser remains unstable because ApplicationRef.isStable has not emitted true within Angular’s documented 10-second threshold during hydration. |
Look for pending asynchronous work, including microtasks and macrotasks. |
If both appear, determine whether the custom zone changes stability timing, whether asynchronous work remains pending, and which application phase reports each message. Neither warning alone establishes that the rendered DOM has a hydration mismatch.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the warning does not establish
- It does not prove that the server-rendered DOM differs from the client’s expected DOM.
- It does not establish that a particular Angular or Zone.js version is affected or that upgrading to a specific release will fix it.
- It does not provide a universal event timing value for custom implementations.
For the relevant API details, consult Angular’s NgZone API reference. The Angular Error Encyclopedia lists NG05000 alongside other documented errors.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
