2025-07-17 17:31:38 +00:00
|
|
|
## API Report File for "core_errors"
|
2022-01-10 14:09:41 -08:00
|
|
|
|
|
|
|
|
> Do not edit this file. It is a report generated by [API Extractor](https://api-extractor.com/).
|
|
|
|
|
|
|
|
|
|
```ts
|
|
|
|
|
|
|
|
|
|
// @public
|
2022-01-21 13:02:40 -08:00
|
|
|
export function formatRuntimeError<T extends number = RuntimeErrorCode>(code: T, message: null | false | string): string;
|
2022-01-10 14:09:41 -08:00
|
|
|
|
2025-03-23 21:36:37 -07:00
|
|
|
// @public (undocumented)
|
|
|
|
|
export function formatRuntimeErrorCode<T extends number = RuntimeErrorCode>(code: T): string;
|
|
|
|
|
|
2022-01-21 13:02:40 -08:00
|
|
|
// @public
|
|
|
|
|
export class RuntimeError<T extends number = RuntimeErrorCode> extends Error {
|
|
|
|
|
constructor(code: T, message: null | false | string);
|
2022-01-10 14:09:41 -08:00
|
|
|
// (undocumented)
|
|
|
|
|
code: T;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// @public
|
|
|
|
|
export const enum RuntimeErrorCode {
|
2025-07-09 14:52:29 -07:00
|
|
|
// (undocumented)
|
|
|
|
|
ANIMATE_INVALID_VALUE = 650,
|
2022-01-10 14:09:41 -08:00
|
|
|
// (undocumented)
|
2022-04-04 21:28:01 -07:00
|
|
|
APPLICATION_REF_ALREADY_DESTROYED = 406,
|
2022-01-10 14:09:41 -08:00
|
|
|
// (undocumented)
|
2023-10-10 14:21:00 +00:00
|
|
|
ASSERTION_NOT_INSIDE_REACTIVE_CONTEXT = -602,
|
2023-10-05 12:06:53 +00:00
|
|
|
// (undocumented)
|
2022-01-10 14:09:41 -08:00
|
|
|
ASYNC_INITIALIZERS_STILL_RUNNING = 405,
|
|
|
|
|
// (undocumented)
|
2022-12-14 12:19:20 +02:00
|
|
|
BOOTSTRAP_COMPONENTS_NOT_FOUND = -403,
|
2022-01-10 14:09:41 -08:00
|
|
|
// (undocumented)
|
2023-04-25 00:32:38 +02:00
|
|
|
COMPONENT_ID_COLLISION = -912,
|
|
|
|
|
// (undocumented)
|
2022-01-10 14:09:41 -08:00
|
|
|
CYCLIC_DI_DEPENDENCY = -200,
|
|
|
|
|
// (undocumented)
|
2025-12-14 12:10:48 -05:00
|
|
|
DEF_TYPE_UNDEFINED = -919,
|
2025-12-10 21:48:29 +01:00
|
|
|
// (undocumented)
|
2025-03-23 21:36:37 -07:00
|
|
|
DEFER_IN_HMR_MODE = -751,
|
|
|
|
|
// (undocumented)
|
2024-12-20 12:20:51 -05:00
|
|
|
DEFER_LOADING_FAILED = -750,
|
2023-10-22 21:26:32 -07:00
|
|
|
// (undocumented)
|
2023-10-17 21:02:01 +02:00
|
|
|
DUPLICATE_DIRECTIVE = 309,
|
2022-09-30 09:24:34 +02:00
|
|
|
// (undocumented)
|
2026-01-02 14:43:58 -05:00
|
|
|
DUPLICATE_NG_MODULE_ID = 921,
|
|
|
|
|
// (undocumented)
|
2022-01-10 14:09:41 -08:00
|
|
|
EXPORT_NOT_FOUND = -301,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
EXPRESSION_CHANGED_AFTER_CHECKED = -100,
|
|
|
|
|
// (undocumented)
|
2025-08-04 19:13:32 +00:00
|
|
|
EXTERNAL_RESOURCE_LOADING_FAILED = 918,
|
|
|
|
|
// (undocumented)
|
2022-09-30 09:24:34 +02:00
|
|
|
HOST_DIRECTIVE_COMPONENT = 310,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
HOST_DIRECTIVE_CONFLICTING_ALIAS = 312,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
HOST_DIRECTIVE_NOT_STANDALONE = 308,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
HOST_DIRECTIVE_UNDEFINED_BINDING = 311,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
HOST_DIRECTIVE_UNRESOLVABLE = 307,
|
|
|
|
|
// (undocumented)
|
2023-04-03 16:26:37 -04:00
|
|
|
HYDRATION_MISSING_NODE = -502,
|
2023-03-20 10:39:10 -07:00
|
|
|
// (undocumented)
|
fix(core): throw coded RuntimeErrors instead of crashing when hydration/rendering can't find an expected DOM node
This started from a real production crash trace:
TypeError: Cannot read properties of null (reading 'nextSibling')
Traced through a minified bundle back to siblingAfter() in
packages/core/src/hydration/node_lookup_utils.ts. It walks forward a
fixed number of DOM siblings during hydration, based on how many the
server rendered. Its only guard, validateSiblingNodeExists(), is
gated behind ngDevMode and stripped from production builds. If the
client DOM has fewer real siblings than the server-serialized data
expects — client/server render diverged, or something outside
Angular (a browser extension, an injected script) removed a node —
the loop ran fully unguarded in production: currentNode went null
partway through, and the next iteration's currentNode.nextSibling
threw a raw, uncoded TypeError instead of a coded, debuggable one.
Reproduced first, not just theorized: added a test that server-
renders a @for loop with 3 items, removes 2 of them before hydration
runs, and confirmed it actually throws that exact TypeError against
the original code before touching anything.
Fix: add a null check at the top of the loop, matching the pattern
already used for the existing NG0500/NG0502 hydration checks in
element.ts — the dev-mode check runs first as before (a no-op in
production), and the new check is a pure safety net that only fires
once that dev-mode check has already been compiled away. In dev mode
this is provably dead code, so nothing about dev behavior changes.
Coded as NG0501 (HYDRATION_MISSING_SIBLINGS, already existed).
While investigating, found and fixed two more call sites with the
exact same shape of bug — a dev-only check that leaves production
completely unguarded:
- navigateToNode() (same file): walks an explicit "firstChild /
nextSibling" navigation path recorded for nodes that can't rely on
simple sibling-walking (e.g. content right after an <ng-content>
slot). Its only guard was also ngDevMode-only. Added the same
production safety net, both mid-loop (the raw-crash case) and
post-loop (where it could previously return null silently despite
the function's return type promising a non-null RNode). New code:
NG0509 (HYDRATION_MISSING_NODE_ON_PATH).
- getParentRElement() (render3/node_manipulation.ts): typed its
tNode parameter as always non-null, but a real production trace
showed it can be null at runtime, crashing on tNode.parent with no
useful information. Widened the type to TNode | null and added a
guard that throws a coded error instead. New code: NG0510
(PARENT_NODE_NOT_FOUND).
Unlike the other two, this one isn't gated behind ngDevMode at all
in the original code — it reproduces unconditionally. Decoded the
actual production minified stack trace against this source
(matched every frame character-for-character) to find the real
cause instead of guessing: an @if/@switch branch's content is its
own embedded template with its own TView, built lazily the first
time that branch renders. If an error interrupts that first pass —
here, a hydration mismatch on the branch's second child, after the
first child's TNode was already created — TView.firstCreatePass
still gets flipped to false in render.ts's `catch` block before the
error propagates, permanently marking that TView as corrupted.
Unlike a component's TView (rebuilt from scratch next time via
getOrCreateComponentTView()'s incompleteFirstPass check), nothing
rebuilds an embedded view's TView. The next time that exact branch
is selected again, its instructions read straight from the
corrupted tView.data instead of creating a fresh TNode, and any
node past the interruption point is still null.
The real test added for this (full_app_hydration_spec.ts) exercises
that whole chain for real: a hydration mismatch on an @if branch's
second child, then re-entering the same branch. Confirmed it throws
the exact byte-for-byte production error message ("Cannot read
properties of null (reading 'parent')") without the fix, and the
coded NG0510 with it. This replaces an earlier synthetic unit test
that just cast a variable to null to bypass the type system rather
than reproducing the actual failure.
Note: a more thorough fix would rebuild the corrupted embedded TView
itself (mirroring getOrCreateComponentTView()), which does make the
crash disappear — but doing that surfaces a second, separate bug:
the aborted first attempt's partially-created LView/DOM is never
torn down, so the retried branch's content gets appended alongside
leftover orphaned nodes instead of replacing them, corrupting
content silently instead of crashing loudly. That's a materially
bigger fix (proper LView cleanup after a mid-creation exception) and
is intentionally out of scope here; this commit keeps the narrower,
safe fix (a clear coded error) rather than trading a loud crash for
silent data corruption.
Along the way, deduplicated describeDomNode(), which existed as two
near-identical private copies (one in this file's own NG0500 check,
one in platform-browser's dom_renderer.ts insertBefore check) and
moved it into core's hydration/error_handling.ts, shared via the
private ɵdescribeDomNode export.
That function was then removed from every production code path
entirely, per review feedback: computing a human-readable node
description is debug-oriented work that shouldn't ship unconditionally
in production bundles, regardless of how cheap it is — production
should get the bare coded error only, the same as everywhere else in
this file. All three fixes above follow that: ngDevMode && 'message'
in production, no computed description. Confirmed the removal
actually shrinks output, not just assumed it: regenerated all 8
affected bundling symbol goldens, and each one shows exactly one
symbol removed — "describeDomNode" — and nothing else.
(cherry picked from commit 83f7695b2e4e1cab347f7817da4ae4262dade415)
2026-08-19 09:40:48 +03:00
|
|
|
HYDRATION_MISSING_NODE_ON_PATH = 509,
|
|
|
|
|
// (undocumented)
|
2023-04-03 16:26:37 -04:00
|
|
|
HYDRATION_MISSING_SIBLINGS = -501,
|
2023-03-20 10:39:10 -07:00
|
|
|
// (undocumented)
|
2023-04-03 14:15:13 -04:00
|
|
|
HYDRATION_NODE_MISMATCH = -500,
|
2023-03-20 10:39:10 -07:00
|
|
|
// (undocumented)
|
2023-05-14 23:48:10 +02:00
|
|
|
HYDRATION_STABLE_TIMEDOUT = -506,
|
|
|
|
|
// (undocumented)
|
2023-09-19 02:09:24 -07:00
|
|
|
IMAGE_PERFORMANCE_WARNING = -913,
|
|
|
|
|
// (undocumented)
|
2022-05-02 15:27:28 +02:00
|
|
|
IMPORT_PROVIDERS_FROM_STANDALONE = 800,
|
|
|
|
|
// (undocumented)
|
2023-10-11 13:54:06 -07:00
|
|
|
INFINITE_CHANGE_DETECTION = 103,
|
|
|
|
|
// (undocumented)
|
2026-02-20 13:01:11 -05:00
|
|
|
INJECTOR_ALREADY_DESTROYED = -205,
|
2021-12-02 05:45:32 +05:30
|
|
|
// (undocumented)
|
2025-09-17 17:53:02 +02:00
|
|
|
INVALID_APP_ID = 211,
|
|
|
|
|
// (undocumented)
|
2025-02-26 12:47:19 +01:00
|
|
|
INVALID_BINDING_TARGET = 316,
|
|
|
|
|
// (undocumented)
|
2021-12-02 05:45:32 +05:30
|
|
|
INVALID_DIFFER_INPUT = 900,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
INVALID_EVENT_BINDING = 306,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
INVALID_FACTORY_DEPENDENCY = 202,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
INVALID_I18N_STRUCTURE = 700,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
INVALID_INHERITANCE = 903,
|
|
|
|
|
// (undocumented)
|
2026-02-20 13:01:11 -05:00
|
|
|
INVALID_INJECTION_TOKEN = -204,
|
2021-12-02 05:45:32 +05:30
|
|
|
// (undocumented)
|
2022-11-28 14:43:18 -08:00
|
|
|
INVALID_MULTI_PROVIDER = -209,
|
2022-07-13 12:31:37 -07:00
|
|
|
// (undocumented)
|
2026-03-09 13:21:52 -07:00
|
|
|
INVALID_RESOURCE_CREATION_IN_PARAMS = 992,
|
|
|
|
|
// (undocumented)
|
2025-02-27 08:17:29 +01:00
|
|
|
INVALID_SET_INPUT_CALL = 317,
|
|
|
|
|
// (undocumented)
|
2023-04-03 16:29:22 -04:00
|
|
|
INVALID_SKIP_HYDRATION_HOST = -504,
|
2023-03-20 10:39:10 -07:00
|
|
|
// (undocumented)
|
2026-07-26 21:03:37 +03:00
|
|
|
INVALID_STYLE_PROP_VALUE = -318,
|
|
|
|
|
// (undocumented)
|
2024-04-30 14:50:35 +02:00
|
|
|
LOOP_TRACK_DUPLICATE_KEYS = -955,
|
2024-04-08 13:17:25 +02:00
|
|
|
// (undocumented)
|
2024-04-30 14:50:35 +02:00
|
|
|
LOOP_TRACK_RECREATE = -956,
|
2024-04-11 10:45:11 +02:00
|
|
|
// (undocumented)
|
2024-10-29 20:51:22 -07:00
|
|
|
MISCONFIGURED_INCREMENTAL_HYDRATION = 508,
|
|
|
|
|
// (undocumented)
|
2025-02-24 19:31:35 +02:00
|
|
|
MISSING_DIRECTIVE_DEFINITION = 916,
|
|
|
|
|
// (undocumented)
|
2023-05-04 17:16:41 +02:00
|
|
|
MISSING_DOCUMENT = 210,
|
|
|
|
|
// (undocumented)
|
2022-04-20 19:31:35 -07:00
|
|
|
MISSING_GENERATED_DEF = 906,
|
|
|
|
|
// (undocumented)
|
2023-04-06 17:54:09 -07:00
|
|
|
MISSING_HYDRATION_ANNOTATIONS = -505,
|
|
|
|
|
// (undocumented)
|
2022-05-27 13:52:34 +02:00
|
|
|
MISSING_INJECTION_CONTEXT = -203,
|
2021-12-02 05:45:32 +05:30
|
|
|
// (undocumented)
|
2022-06-17 07:30:19 +05:30
|
|
|
MISSING_INJECTION_TOKEN = 208,
|
|
|
|
|
// (undocumented)
|
2022-06-23 10:43:03 +05:30
|
|
|
MISSING_LOCALE_DATA = 701,
|
|
|
|
|
// (undocumented)
|
2025-02-24 19:31:35 +02:00
|
|
|
MISSING_NG_MODULE_DEFINITION = 915,
|
|
|
|
|
// (undocumented)
|
2023-03-08 12:25:22 -08:00
|
|
|
MISSING_REQUIRED_INJECTABLE_IN_BOOTSTRAP = 402,
|
|
|
|
|
// (undocumented)
|
2023-08-13 11:48:18 +02:00
|
|
|
MISSING_SSR_CONTENT_INTEGRITY_MARKER = -507,
|
2023-07-26 00:16:47 +02:00
|
|
|
// (undocumented)
|
2022-06-23 22:20:02 +05:30
|
|
|
MISSING_ZONEJS = 908,
|
|
|
|
|
// (undocumented)
|
2022-01-10 14:09:41 -08:00
|
|
|
MULTIPLE_COMPONENTS_MATCH = -300,
|
|
|
|
|
// (undocumented)
|
2023-05-20 22:09:21 +02:00
|
|
|
MULTIPLE_MATCHING_PIPES = 313,
|
|
|
|
|
// (undocumented)
|
2022-01-10 14:09:41 -08:00
|
|
|
MULTIPLE_PLATFORMS = 400,
|
|
|
|
|
// (undocumented)
|
2025-05-21 14:48:33 +03:00
|
|
|
MUST_PROVIDE_STREAM_OPTION = 990,
|
|
|
|
|
// (undocumented)
|
2026-01-02 14:43:58 -05:00
|
|
|
NG_MODULE_ID_NOT_FOUND = 920,
|
|
|
|
|
// (undocumented)
|
2025-02-26 12:47:19 +01:00
|
|
|
NO_BINDING_TARGET = 315,
|
|
|
|
|
// (undocumented)
|
2021-12-02 05:45:32 +05:30
|
|
|
NO_SUPPORTING_DIFFER_FACTORY = 901,
|
|
|
|
|
// (undocumented)
|
2024-02-28 15:06:44 +00:00
|
|
|
OUTPUT_REF_DESTROYED = 953,
|
|
|
|
|
// (undocumented)
|
fix(core): throw coded RuntimeErrors instead of crashing when hydration/rendering can't find an expected DOM node
This started from a real production crash trace:
TypeError: Cannot read properties of null (reading 'nextSibling')
Traced through a minified bundle back to siblingAfter() in
packages/core/src/hydration/node_lookup_utils.ts. It walks forward a
fixed number of DOM siblings during hydration, based on how many the
server rendered. Its only guard, validateSiblingNodeExists(), is
gated behind ngDevMode and stripped from production builds. If the
client DOM has fewer real siblings than the server-serialized data
expects — client/server render diverged, or something outside
Angular (a browser extension, an injected script) removed a node —
the loop ran fully unguarded in production: currentNode went null
partway through, and the next iteration's currentNode.nextSibling
threw a raw, uncoded TypeError instead of a coded, debuggable one.
Reproduced first, not just theorized: added a test that server-
renders a @for loop with 3 items, removes 2 of them before hydration
runs, and confirmed it actually throws that exact TypeError against
the original code before touching anything.
Fix: add a null check at the top of the loop, matching the pattern
already used for the existing NG0500/NG0502 hydration checks in
element.ts — the dev-mode check runs first as before (a no-op in
production), and the new check is a pure safety net that only fires
once that dev-mode check has already been compiled away. In dev mode
this is provably dead code, so nothing about dev behavior changes.
Coded as NG0501 (HYDRATION_MISSING_SIBLINGS, already existed).
While investigating, found and fixed two more call sites with the
exact same shape of bug — a dev-only check that leaves production
completely unguarded:
- navigateToNode() (same file): walks an explicit "firstChild /
nextSibling" navigation path recorded for nodes that can't rely on
simple sibling-walking (e.g. content right after an <ng-content>
slot). Its only guard was also ngDevMode-only. Added the same
production safety net, both mid-loop (the raw-crash case) and
post-loop (where it could previously return null silently despite
the function's return type promising a non-null RNode). New code:
NG0509 (HYDRATION_MISSING_NODE_ON_PATH).
- getParentRElement() (render3/node_manipulation.ts): typed its
tNode parameter as always non-null, but a real production trace
showed it can be null at runtime, crashing on tNode.parent with no
useful information. Widened the type to TNode | null and added a
guard that throws a coded error instead. New code: NG0510
(PARENT_NODE_NOT_FOUND).
Unlike the other two, this one isn't gated behind ngDevMode at all
in the original code — it reproduces unconditionally. Decoded the
actual production minified stack trace against this source
(matched every frame character-for-character) to find the real
cause instead of guessing: an @if/@switch branch's content is its
own embedded template with its own TView, built lazily the first
time that branch renders. If an error interrupts that first pass —
here, a hydration mismatch on the branch's second child, after the
first child's TNode was already created — TView.firstCreatePass
still gets flipped to false in render.ts's `catch` block before the
error propagates, permanently marking that TView as corrupted.
Unlike a component's TView (rebuilt from scratch next time via
getOrCreateComponentTView()'s incompleteFirstPass check), nothing
rebuilds an embedded view's TView. The next time that exact branch
is selected again, its instructions read straight from the
corrupted tView.data instead of creating a fresh TNode, and any
node past the interruption point is still null.
The real test added for this (full_app_hydration_spec.ts) exercises
that whole chain for real: a hydration mismatch on an @if branch's
second child, then re-entering the same branch. Confirmed it throws
the exact byte-for-byte production error message ("Cannot read
properties of null (reading 'parent')") without the fix, and the
coded NG0510 with it. This replaces an earlier synthetic unit test
that just cast a variable to null to bypass the type system rather
than reproducing the actual failure.
Note: a more thorough fix would rebuild the corrupted embedded TView
itself (mirroring getOrCreateComponentTView()), which does make the
crash disappear — but doing that surfaces a second, separate bug:
the aborted first attempt's partially-created LView/DOM is never
torn down, so the retried branch's content gets appended alongside
leftover orphaned nodes instead of replacing them, corrupting
content silently instead of crashing loudly. That's a materially
bigger fix (proper LView cleanup after a mid-creation exception) and
is intentionally out of scope here; this commit keeps the narrower,
safe fix (a clear coded error) rather than trading a loud crash for
silent data corruption.
Along the way, deduplicated describeDomNode(), which existed as two
near-identical private copies (one in this file's own NG0500 check,
one in platform-browser's dom_renderer.ts insertBefore check) and
moved it into core's hydration/error_handling.ts, shared via the
private ɵdescribeDomNode export.
That function was then removed from every production code path
entirely, per review feedback: computing a human-readable node
description is debug-oriented work that shouldn't ship unconditionally
in production bundles, regardless of how cheap it is — production
should get the bare coded error only, the same as everywhere else in
this file. All three fixes above follow that: ngDevMode && 'message'
in production, no computed description. Confirmed the removal
actually shrinks output, not just assumed it: regenerated all 8
affected bundling symbol goldens, and each one shows exactly one
symbol removed — "describeDomNode" — and nothing else.
(cherry picked from commit 83f7695b2e4e1cab347f7817da4ae4262dade415)
2026-08-19 09:40:48 +03:00
|
|
|
PARENT_NODE_NOT_FOUND = 510,
|
|
|
|
|
// (undocumented)
|
2022-01-10 14:09:41 -08:00
|
|
|
PIPE_NOT_FOUND = -302,
|
|
|
|
|
// (undocumented)
|
2022-04-04 21:28:01 -07:00
|
|
|
PLATFORM_ALREADY_DESTROYED = 404,
|
|
|
|
|
// (undocumented)
|
2025-09-19 15:29:07 +00:00
|
|
|
PLATFORM_NOT_FOUND = -401,
|
2022-01-10 14:09:41 -08:00
|
|
|
// (undocumented)
|
2024-04-18 15:13:23 -07:00
|
|
|
PROVIDED_BOTH_ZONE_AND_ZONELESS = 408,
|
|
|
|
|
// (undocumented)
|
2026-02-20 13:01:11 -05:00
|
|
|
PROVIDER_IN_WRONG_CONTEXT = -207,
|
2022-05-02 07:40:44 -07:00
|
|
|
// (undocumented)
|
2022-01-10 14:09:41 -08:00
|
|
|
PROVIDER_NOT_FOUND = -201,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
RECURSIVE_APPLICATION_REF_TICK = 101,
|
|
|
|
|
// (undocumented)
|
2022-06-29 12:01:33 -07:00
|
|
|
RENDERER_NOT_FOUND = 407,
|
|
|
|
|
// (undocumented)
|
2023-04-10 11:21:53 -07:00
|
|
|
REQUIRE_SYNC_WITHOUT_SYNC_EMIT = 601,
|
|
|
|
|
// (undocumented)
|
2023-12-08 17:32:08 +00:00
|
|
|
REQUIRED_INPUT_NO_VALUE = -950,
|
|
|
|
|
// (undocumented)
|
2024-06-13 21:26:10 +02:00
|
|
|
REQUIRED_MODEL_NO_VALUE = 952,
|
2024-02-05 19:18:10 +01:00
|
|
|
// (undocumented)
|
2024-02-06 23:00:30 +01:00
|
|
|
REQUIRED_QUERY_NO_VALUE = -951,
|
|
|
|
|
// (undocumented)
|
2026-08-19 08:41:09 +03:00
|
|
|
RESOURCE_COMPLETED_BEFORE_PRODUCING_VALUE = -991,
|
2025-05-21 14:48:33 +03:00
|
|
|
// (undocumented)
|
2024-02-27 09:34:43 +01:00
|
|
|
RUNTIME_DEPS_INVALID_IMPORTED_TYPE = 980,
|
2023-07-17 16:45:29 -04:00
|
|
|
// (undocumented)
|
2024-02-27 09:34:43 +01:00
|
|
|
RUNTIME_DEPS_ORPHAN_COMPONENT = 981,
|
2023-09-10 18:41:39 -04:00
|
|
|
// (undocumented)
|
2023-03-27 11:17:57 -07:00
|
|
|
SIGNAL_WRITE_FROM_ILLEGAL_CONTEXT = 600,
|
|
|
|
|
// (undocumented)
|
2022-01-10 14:09:41 -08:00
|
|
|
TEMPLATE_STRUCTURE_ERROR = 305,
|
|
|
|
|
// (undocumented)
|
2022-04-20 19:31:35 -07:00
|
|
|
TYPE_IS_NOT_STANDALONE = 907,
|
|
|
|
|
// (undocumented)
|
2022-06-23 22:20:02 +05:30
|
|
|
UNEXPECTED_ZONE_STATE = 909,
|
|
|
|
|
// (undocumented)
|
2024-05-15 22:32:54 +02:00
|
|
|
UNEXPECTED_ZONEJS_PRESENT_IN_ZONELESS_MODE = 914,
|
|
|
|
|
// (undocumented)
|
2024-05-14 14:42:21 +02:00
|
|
|
UNINITIALIZED_LET_ACCESS = 314,
|
|
|
|
|
// (undocumented)
|
2022-01-10 14:09:41 -08:00
|
|
|
UNKNOWN_BINDING = 303,
|
|
|
|
|
// (undocumented)
|
2021-12-02 05:45:32 +05:30
|
|
|
UNKNOWN_ELEMENT = 304,
|
|
|
|
|
// (undocumented)
|
2025-12-01 10:26:56 +01:00
|
|
|
UNSAFE_ATTRIBUTE_BINDING = -910,
|
2022-10-25 14:45:32 -07:00
|
|
|
// (undocumented)
|
2021-12-02 05:45:32 +05:30
|
|
|
UNSAFE_VALUE_IN_RESOURCE_URL = 904,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
UNSAFE_VALUE_IN_SCRIPT = 905,
|
|
|
|
|
// (undocumented)
|
2023-04-03 16:28:18 -04:00
|
|
|
UNSUPPORTED_PROJECTION_DOM_NODES = -503,
|
2023-03-20 10:39:10 -07:00
|
|
|
// (undocumented)
|
2023-04-12 10:19:30 +02:00
|
|
|
VIEW_ALREADY_ATTACHED = 902,
|
|
|
|
|
// (undocumented)
|
2026-01-02 14:43:58 -05:00
|
|
|
VIEW_ALREADY_DESTROYED = 911,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
VIEW_DESTROYED_INSERT_ERROR = 922,
|
|
|
|
|
// (undocumented)
|
|
|
|
|
VIEW_DESTROYED_MOVE_ERROR = 923
|
2022-01-10 14:09:41 -08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// (No @packageDocumentation comment for this package)
|
|
|
|
|
|
|
|
|
|
```
|