Skip to content

Commit d8e42be

Browse files
committed
doc: move ERR_INVALID_PERFORMANCE_MARK to legacy errors
PR-URL: #55247 Refs: #14680 Refs: #39297 Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
1 parent 6fcac73 commit d8e42be

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

doc/api/errors.md

+12-7
Original file line numberDiff line numberDiff line change
@@ -2016,13 +2016,6 @@ An invalid [`package.json`][] file failed parsing.
20162016
The `package.json` [`"exports"`][] field contains an invalid target mapping
20172017
value for the attempted module resolution.
20182018

2019-
<a id="ERR_INVALID_PERFORMANCE_MARK"></a>
2020-
2021-
### `ERR_INVALID_PERFORMANCE_MARK`
2022-
2023-
While using the Performance Timing API (`perf_hooks`), a performance mark is
2024-
invalid.
2025-
20262019
<a id="ERR_INVALID_PROTOCOL"></a>
20272020

20282021
### `ERR_INVALID_PROTOCOL`
@@ -3449,6 +3442,18 @@ removed: v15.0.0
34493442

34503443
An invalid or unknown file encoding was passed.
34513444

3445+
<a id="ERR_INVALID_PERFORMANCE_MARK"></a>
3446+
3447+
### `ERR_INVALID_PERFORMANCE_MARK`
3448+
3449+
<!-- YAML
3450+
added: v8.5.0
3451+
removed: v16.7.0
3452+
-->
3453+
3454+
While using the Performance Timing API (`perf_hooks`), a performance mark is
3455+
invalid.
3456+
34523457
<a id="ERR_INVALID_TRANSFER_OBJECT"></a>
34533458

34543459
### `ERR_INVALID_TRANSFER_OBJECT`

0 commit comments

Comments
 (0)