1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
|
# Errors
<!--introduced_in=v4.0.0-->
<!--type=misc-->
Applications running in Node.js will generally experience four categories of
errors:
* Standard JavaScript errors such as {EvalError}, {SyntaxError}, {RangeError},
{ReferenceError}, {TypeError}, and {URIError}.
* System errors triggered by underlying operating system constraints such
as attempting to open a file that does not exist or attempting to send data
over a closed socket.
* User-specified errors triggered by application code.
* `AssertionError`s are a special class of error that can be triggered when
Node.js detects an exceptional logic violation that should never occur. These
are raised typically by the `assert` module.
All JavaScript and System errors raised by Node.js inherit from, or are
instances of, the standard JavaScript {Error} class and are guaranteed
to provide *at least* the properties available on that class.
## Error Propagation and Interception
<!--type=misc-->
Node.js supports several mechanisms for propagating and handling errors that
occur while an application is running. How these errors are reported and
handled depends entirely on the type of `Error` and the style of the API that is
called.
All JavaScript errors are handled as exceptions that *immediately* generate
and throw an error using the standard JavaScript `throw` mechanism. These
are handled using the [`try…catch` construct][try-catch] provided by the
JavaScript language.
```js
// Throws with a ReferenceError because z is not defined.
try {
const m = 1;
const n = m + z;
} catch (err) {
// Handle the error here.
}
```
Any use of the JavaScript `throw` mechanism will raise an exception that
*must* be handled using `try…catch` or the Node.js process will exit
immediately.
With few exceptions, _Synchronous_ APIs (any blocking method that does not
accept a `callback` function, such as [`fs.readFileSync`][]), will use `throw`
to report errors.
Errors that occur within _Asynchronous APIs_ may be reported in multiple ways:
* Most asynchronous methods that accept a `callback` function will accept an
`Error` object passed as the first argument to that function. If that first
argument is not `null` and is an instance of `Error`, then an error occurred
that should be handled.
<!-- eslint-disable no-useless-return -->
```js
const fs = require('fs');
fs.readFile('a file that does not exist', (err, data) => {
if (err) {
console.error('There was an error reading the file!', err);
return;
}
// Otherwise handle the data
});
```
* When an asynchronous method is called on an object that is an
[`EventEmitter`][], errors can be routed to that object's `'error'` event.
```js
const net = require('net');
const connection = net.connect('localhost');
// Adding an 'error' event handler to a stream:
connection.on('error', (err) => {
// If the connection is reset by the server, or if it can't
// connect at all, or on any sort of error encountered by
// the connection, the error will be sent here.
console.error(err);
});
connection.pipe(process.stdout);
```
* A handful of typically asynchronous methods in the Node.js API may still
use the `throw` mechanism to raise exceptions that must be handled using
`try…catch`. There is no comprehensive list of such methods; please
refer to the documentation of each method to determine the appropriate
error handling mechanism required.
The use of the `'error'` event mechanism is most common for [stream-based][]
and [event emitter-based][] APIs, which themselves represent a series of
asynchronous operations over time (as opposed to a single operation that may
pass or fail).
For *all* [`EventEmitter`][] objects, if an `'error'` event handler is not
provided, the error will be thrown, causing the Node.js process to report an
uncaught exception and crash unless either: The [`domain`][domains] module is
used appropriately or a handler has been registered for the
[`'uncaughtException'`][] event.
```js
const EventEmitter = require('events');
const ee = new EventEmitter();
setImmediate(() => {
// This will crash the process because no 'error' event
// handler has been added.
ee.emit('error', new Error('This will crash'));
});
```
Errors generated in this way *cannot* be intercepted using `try…catch` as
they are thrown *after* the calling code has already exited.
Developers must refer to the documentation for each method to determine
exactly how errors raised by those methods are propagated.
### Error-first callbacks
<!--type=misc-->
Most asynchronous methods exposed by the Node.js core API follow an idiomatic
pattern referred to as an _error-first callback_. With this pattern, a callback
function is passed to the method as an argument. When the operation either
completes or an error is raised, the callback function is called with the
`Error` object (if any) passed as the first argument. If no error was raised,
the first argument will be passed as `null`.
```js
const fs = require('fs');
function errorFirstCallback(err, data) {
if (err) {
console.error('There was an error', err);
return;
}
console.log(data);
}
fs.readFile('/some/file/that/does-not-exist', errorFirstCallback);
fs.readFile('/some/file/that/does-exist', errorFirstCallback);
```
The JavaScript `try…catch` mechanism **cannot** be used to intercept errors
generated by asynchronous APIs. A common mistake for beginners is to try to
use `throw` inside an error-first callback:
```js
// THIS WILL NOT WORK:
const fs = require('fs');
try {
fs.readFile('/some/file/that/does-not-exist', (err, data) => {
// Mistaken assumption: throwing here...
if (err) {
throw err;
}
});
} catch (err) {
// This will not catch the throw!
console.error(err);
}
```
This will not work because the callback function passed to `fs.readFile()` is
called asynchronously. By the time the callback has been called, the
surrounding code, including the `try…catch` block, will have already exited.
Throwing an error inside the callback **can crash the Node.js process** in most
cases. If [domains][] are enabled, or a handler has been registered with
`process.on('uncaughtException')`, such errors can be intercepted.
## Class: `Error`
<!--type=class-->
A generic JavaScript {Error} object that does not denote any specific
circumstance of why the error occurred. `Error` objects capture a "stack trace"
detailing the point in the code at which the `Error` was instantiated, and may
provide a text description of the error.
All errors generated by Node.js, including all System and JavaScript errors,
will either be instances of, or inherit from, the `Error` class.
### `new Error(message)`
* `message` {string}
Creates a new `Error` object and sets the `error.message` property to the
provided text message. If an object is passed as `message`, the text message
is generated by calling `message.toString()`. The `error.stack` property will
represent the point in the code at which `new Error()` was called. Stack traces
are dependent on [V8's stack trace API][]. Stack traces extend only to either
(a) the beginning of *synchronous code execution*, or (b) the number of frames
given by the property `Error.stackTraceLimit`, whichever is smaller.
### `Error.captureStackTrace(targetObject[, constructorOpt])`
* `targetObject` {Object}
* `constructorOpt` {Function}
Creates a `.stack` property on `targetObject`, which when accessed returns
a string representing the location in the code at which
`Error.captureStackTrace()` was called.
```js
const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack; // Similar to `new Error().stack`
```
The first line of the trace will be prefixed with
`${myObject.name}: ${myObject.message}`.
The optional `constructorOpt` argument accepts a function. If given, all frames
above `constructorOpt`, including `constructorOpt`, will be omitted from the
generated stack trace.
The `constructorOpt` argument is useful for hiding implementation
details of error generation from an end user. For instance:
```js
function MyError() {
Error.captureStackTrace(this, MyError);
}
// Without passing MyError to captureStackTrace, the MyError
// frame would show up in the .stack property. By passing
// the constructor, we omit that frame, and retain all frames below it.
new MyError().stack;
```
### `Error.stackTraceLimit`
* {number}
The `Error.stackTraceLimit` property specifies the number of stack frames
collected by a stack trace (whether generated by `new Error().stack` or
`Error.captureStackTrace(obj)`).
The default value is `10` but may be set to any valid JavaScript number. Changes
will affect any stack trace captured *after* the value has been changed.
If set to a non-number value, or set to a negative number, stack traces will
not capture any frames.
### `error.code`
* {string}
The `error.code` property is a string label that identifies the kind of error.
`error.code` is the most stable way to identify an error. It will only change
between major versions of Node.js. In contrast, `error.message` strings may
change between any versions of Node.js. See [Node.js Error Codes][] for details
about specific codes.
### `error.message`
* {string}
The `error.message` property is the string description of the error as set by
calling `new Error(message)`. The `message` passed to the constructor will also
appear in the first line of the stack trace of the `Error`, however changing
this property after the `Error` object is created *may not* change the first
line of the stack trace (for example, when `error.stack` is read before this
property is changed).
```js
const err = new Error('The message');
console.error(err.message);
// Prints: The message
```
### `error.stack`
* {string}
The `error.stack` property is a string describing the point in the code at which
the `Error` was instantiated.
```txt
Error: Things keep happening!
at /home/gbusey/file.js:525:2
at Frobnicator.refrobulate (/home/gbusey/business-logic.js:424:21)
at Actor.<anonymous> (/home/gbusey/actors.js:400:8)
at increaseSynergy (/home/gbusey/actors.js:701:6)
```
The first line is formatted as `<error class name>: <error message>`, and
is followed by a series of stack frames (each line beginning with "at ").
Each frame describes a call site within the code that lead to the error being
generated. V8 attempts to display a name for each function (by variable name,
function name, or object method name), but occasionally it will not be able to
find a suitable name. If V8 cannot determine a name for the function, only
location information will be displayed for that frame. Otherwise, the
determined function name will be displayed with location information appended
in parentheses.
Frames are only generated for JavaScript functions. If, for example, execution
synchronously passes through a C++ addon function called `cheetahify` which
itself calls a JavaScript function, the frame representing the `cheetahify` call
will not be present in the stack traces:
```js
const cheetahify = require('./native-binding.node');
function makeFaster() {
// `cheetahify()` *synchronously* calls speedy.
cheetahify(function speedy() {
throw new Error('oh no!');
});
}
makeFaster();
// will throw:
// /home/gbusey/file.js:6
// throw new Error('oh no!');
// ^
// Error: oh no!
// at speedy (/home/gbusey/file.js:6:11)
// at makeFaster (/home/gbusey/file.js:5:3)
// at Object.<anonymous> (/home/gbusey/file.js:10:1)
// at Module._compile (module.js:456:26)
// at Object.Module._extensions..js (module.js:474:10)
// at Module.load (module.js:356:32)
// at Function.Module._load (module.js:312:12)
// at Function.Module.runMain (module.js:497:10)
// at startup (node.js:119:16)
// at node.js:906:3
```
The location information will be one of:
* `native`, if the frame represents a call internal to V8 (as in `[].forEach`).
* `plain-filename.js:line:column`, if the frame represents a call internal
to Node.js.
* `/absolute/path/to/file.js:line:column`, if the frame represents a call in
a user program, or its dependencies.
The string representing the stack trace is lazily generated when the
`error.stack` property is **accessed**.
The number of frames captured by the stack trace is bounded by the smaller of
`Error.stackTraceLimit` or the number of available frames on the current event
loop tick.
## Class: `AssertionError`
* Extends: {errors.Error}
Indicates the failure of an assertion. For details, see
[`Class: assert.AssertionError`][].
## Class: `RangeError`
* Extends: {errors.Error}
Indicates that a provided argument was not within the set or range of
acceptable values for a function; whether that is a numeric range, or
outside the set of options for a given function parameter.
```js
require('net').connect(-1);
// Throws "RangeError: "port" option should be >= 0 and < 65536: -1"
```
Node.js will generate and throw `RangeError` instances *immediately* as a form
of argument validation.
## Class: `ReferenceError`
* Extends: {errors.Error}
Indicates that an attempt is being made to access a variable that is not
defined. Such errors commonly indicate typos in code, or an otherwise broken
program.
While client code may generate and propagate these errors, in practice, only V8
will do so.
```js
doesNotExist;
// Throws ReferenceError, doesNotExist is not a variable in this program.
```
Unless an application is dynamically generating and running code,
`ReferenceError` instances should always be considered a bug in the code
or its dependencies.
## Class: `SyntaxError`
* Extends: {errors.Error}
Indicates that a program is not valid JavaScript. These errors may only be
generated and propagated as a result of code evaluation. Code evaluation may
happen as a result of `eval`, `Function`, `require`, or [vm][]. These errors
are almost always indicative of a broken program.
```js
try {
require('vm').runInThisContext('binary ! isNotOk');
} catch (err) {
// 'err' will be a SyntaxError.
}
```
`SyntaxError` instances are unrecoverable in the context that created them –
they may only be caught by other contexts.
## Class: `SystemError`
* Extends: {errors.Error}
Node.js generates system errors when exceptions occur within its runtime
environment. These usually occur when an application violates an operating
system constraint. For example, a system error will occur if an application
attempts to read a file that does not exist.
* `address` {string} If present, the address to which a network connection
failed
* `code` {string} The string error code
* `dest` {string} If present, the file path destination when reporting a file
system error
* `errno` {number} The system-provided error number
* `info` {Object} If present, extra details about the error condition
* `message` {string} A system-provided human-readable description of the error
* `path` {string} If present, the file path when reporting a file system error
* `port` {number} If present, the network connection port that is not available
* `syscall` {string} The name of the system call that triggered the error
### `error.address`
* {string}
If present, `error.address` is a string describing the address to which a
network connection failed.
### `error.code`
* {string}
The `error.code` property is a string representing the error code.
### `error.dest`
* {string}
If present, `error.dest` is the file path destination when reporting a file
system error.
### `error.errno`
* {number}
The `error.errno` property is a negative number which corresponds
to the error code defined in [`libuv Error handling`][].
On Windows the error number provided by the system will be normalized by libuv.
To get the string representation of the error code, use
[`util.getSystemErrorName(error.errno)`][].
### `error.info`
* {Object}
If present, `error.info` is an object with details about the error condition.
### `error.message`
* {string}
`error.message` is a system-provided human-readable description of the error.
### `error.path`
* {string}
If present, `error.path` is a string containing a relevant invalid pathname.
### `error.port`
* {number}
If present, `error.port` is the network connection port that is not available.
### `error.syscall`
* {string}
The `error.syscall` property is a string describing the [syscall][] that failed.
### Common System Errors
This is a list of system errors commonly-encountered when writing a Node.js
program. For a comprehensive list, see the [`errno`(3) man page][].
* `EACCES` (Permission denied): An attempt was made to access a file in a way
forbidden by its file access permissions.
* `EADDRINUSE` (Address already in use): An attempt to bind a server
([`net`][], [`http`][], or [`https`][]) to a local address failed due to
another server on the local system already occupying that address.
* `ECONNREFUSED` (Connection refused): No connection could be made because the
target machine actively refused it. This usually results from trying to
connect to a service that is inactive on the foreign host.
* `ECONNRESET` (Connection reset by peer): A connection was forcibly closed by
a peer. This normally results from a loss of the connection on the remote
socket due to a timeout or reboot. Commonly encountered via the [`http`][]
and [`net`][] modules.
* `EEXIST` (File exists): An existing file was the target of an operation that
required that the target not exist.
* `EISDIR` (Is a directory): An operation expected a file, but the given
pathname was a directory.
* `EMFILE` (Too many open files in system): Maximum number of
[file descriptors][] allowable on the system has been reached, and
requests for another descriptor cannot be fulfilled until at least one
has been closed. This is encountered when opening many files at once in
parallel, especially on systems (in particular, macOS) where there is a low
file descriptor limit for processes. To remedy a low limit, run
`ulimit -n 2048` in the same shell that will run the Node.js process.
* `ENOENT` (No such file or directory): Commonly raised by [`fs`][] operations
to indicate that a component of the specified pathname does not exist — no
entity (file or directory) could be found by the given path.
* `ENOTDIR` (Not a directory): A component of the given pathname existed, but
was not a directory as expected. Commonly raised by [`fs.readdir`][].
* `ENOTEMPTY` (Directory not empty): A directory with entries was the target
of an operation that requires an empty directory — usually [`fs.unlink`][].
* `ENOTFOUND` (DNS lookup failed): Indicates a DNS failure of either
`EAI_NODATA` or `EAI_NONAME`. This is not a standard POSIX error.
* `EPERM` (Operation not permitted): An attempt was made to perform an
operation that requires elevated privileges.
* `EPIPE` (Broken pipe): A write on a pipe, socket, or FIFO for which there is
no process to read the data. Commonly encountered at the [`net`][] and
[`http`][] layers, indicative that the remote side of the stream being
written to has been closed.
* `ETIMEDOUT` (Operation timed out): A connect or send request failed because
the connected party did not properly respond after a period of time. Usually
encountered by [`http`][] or [`net`][] — often a sign that a `socket.end()`
was not properly called.
## Class: `TypeError`
* Extends {errors.Error}
Indicates that a provided argument is not an allowable type. For example,
passing a function to a parameter which expects a string would be considered
a `TypeError`.
```js
require('url').parse(() => { });
// Throws TypeError, since it expected a string.
```
Node.js will generate and throw `TypeError` instances *immediately* as a form
of argument validation.
## Exceptions vs. Errors
<!--type=misc-->
A JavaScript exception is a value that is thrown as a result of an invalid
operation or as the target of a `throw` statement. While it is not required
that these values are instances of `Error` or classes which inherit from
`Error`, all exceptions thrown by Node.js or the JavaScript runtime *will* be
instances of `Error`.
Some exceptions are *unrecoverable* at the JavaScript layer. Such exceptions
will *always* cause the Node.js process to crash. Examples include `assert()`
checks or `abort()` calls in the C++ layer.
## OpenSSL Errors
Errors originating in `crypto` or `tls` are of class `Error`, and in addition to
the standard `.code` and `.message` properties, may have some additional
OpenSSL-specific properties.
### `error.opensslErrorStack`
An array of errors that can give context to where in the OpenSSL library an
error originates from.
### `error.function`
The OpenSSL function the error originates in.
### `error.library`
The OpenSSL library the error originates in.
### `error.reason`
A human-readable string describing the reason for the error.
<a id="nodejs-error-codes"></a>
## Node.js Error Codes
<a id="ERR_AMBIGUOUS_ARGUMENT"></a>
### `ERR_AMBIGUOUS_ARGUMENT`
A function argument is being used in a way that suggests that the function
signature may be misunderstood. This is thrown by the `assert` module when the
`message` parameter in `assert.throws(block, message)` matches the error message
thrown by `block` because that usage suggests that the user believes `message`
is the expected message rather than the message the `AssertionError` will
display if `block` does not throw.
<a id="ERR_ARG_NOT_ITERABLE"></a>
### `ERR_ARG_NOT_ITERABLE`
An iterable argument (i.e. a value that works with `for...of` loops) was
required, but not provided to a Node.js API.
<a id="ERR_ASSERTION"></a>
### `ERR_ASSERTION`
A special type of error that can be triggered whenever Node.js detects an
exceptional logic violation that should never occur. These are raised typically
by the `assert` module.
<a id="ERR_ASYNC_CALLBACK"></a>
### `ERR_ASYNC_CALLBACK`
An attempt was made to register something that is not a function as an
`AsyncHooks` callback.
<a id="ERR_ASYNC_TYPE"></a>
### `ERR_ASYNC_TYPE`
The type of an asynchronous resource was invalid. Users are also able
to define their own types if using the public embedder API.
<a id="ERR_BROTLI_COMPRESSION_FAILED"></a>
### `ERR_BROTLI_COMPRESSION_FAILED`
Data passed to a Brotli stream was not successfully compressed.
<a id="ERR_BROTLI_INVALID_PARAM"></a>
### `ERR_BROTLI_INVALID_PARAM`
An invalid parameter key was passed during construction of a Brotli stream.
<a id="ERR_BUFFER_CONTEXT_NOT_AVAILABLE"></a>
### `ERR_BUFFER_CONTEXT_NOT_AVAILABLE`
An attempt was made to create a Node.js `Buffer` instance from addon or embedder
code, while in a JS engine Context that is not associated with a Node.js
instance. The data passed to the `Buffer` method will have been released
by the time the method returns.
When encountering this error, a possible alternative to creating a `Buffer`
instance is to create a normal `Uint8Array`, which only differs in the
prototype of the resulting object. `Uint8Array`s are generally accepted in all
Node.js core APIs where `Buffer`s are; they are available in all Contexts.
<a id="ERR_BUFFER_OUT_OF_BOUNDS"></a>
### `ERR_BUFFER_OUT_OF_BOUNDS`
An operation outside the bounds of a `Buffer` was attempted.
<a id="ERR_BUFFER_TOO_LARGE"></a>
### `ERR_BUFFER_TOO_LARGE`
An attempt has been made to create a `Buffer` larger than the maximum allowed
size.
<a id="ERR_CANNOT_WATCH_SIGINT"></a>
### `ERR_CANNOT_WATCH_SIGINT`
Node.js was unable to watch for the `SIGINT` signal.
<a id="ERR_CHILD_CLOSED_BEFORE_REPLY"></a>
### `ERR_CHILD_CLOSED_BEFORE_REPLY`
A child process was closed before the parent received a reply.
<a id="ERR_CHILD_PROCESS_IPC_REQUIRED"></a>
### `ERR_CHILD_PROCESS_IPC_REQUIRED`
Used when a child process is being forked without specifying an IPC channel.
<a id="ERR_CHILD_PROCESS_STDIO_MAXBUFFER"></a>
### `ERR_CHILD_PROCESS_STDIO_MAXBUFFER`
Used when the main process is trying to read data from the child process's
STDERR/STDOUT, and the data's length is longer than the `maxBuffer` option.
<a id="ERR_CONSOLE_WRITABLE_STREAM"></a>
### `ERR_CONSOLE_WRITABLE_STREAM`
`Console` was instantiated without `stdout` stream, or `Console` has a
non-writable `stdout` or `stderr` stream.
<a id="ERR_CONSTRUCT_CALL_REQUIRED"></a>
### `ERR_CONSTRUCT_CALL_REQUIRED`
A constructor for a class was called without `new`.
<a id="ERR_CONSTRUCT_CALL_INVALID"></a>
### `ERR_CONSTRUCT_CALL_INVALID`
<!--
added: v12.5.0
-->
A class constructor was called that is not callable.
<a id="ERR_CPU_USAGE"></a>
### `ERR_CPU_USAGE`
The native call from `process.cpuUsage` could not be processed.
<a id="ERR_CRYPTO_CUSTOM_ENGINE_NOT_SUPPORTED"></a>
### `ERR_CRYPTO_CUSTOM_ENGINE_NOT_SUPPORTED`
A client certificate engine was requested that is not supported by the version
of OpenSSL being used.
<a id="ERR_CRYPTO_ECDH_INVALID_FORMAT"></a>
### `ERR_CRYPTO_ECDH_INVALID_FORMAT`
An invalid value for the `format` argument was passed to the `crypto.ECDH()`
class `getPublicKey()` method.
<a id="ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY"></a>
### `ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY`
An invalid value for the `key` argument has been passed to the
`crypto.ECDH()` class `computeSecret()` method. It means that the public
key lies outside of the elliptic curve.
<a id="ERR_CRYPTO_ENGINE_UNKNOWN"></a>
### `ERR_CRYPTO_ENGINE_UNKNOWN`
An invalid crypto engine identifier was passed to
[`require('crypto').setEngine()`][].
<a id="ERR_CRYPTO_FIPS_FORCED"></a>
### `ERR_CRYPTO_FIPS_FORCED`
The [`--force-fips`][] command-line argument was used but there was an attempt
to enable or disable FIPS mode in the `crypto` module.
<a id="ERR_CRYPTO_FIPS_UNAVAILABLE"></a>
### `ERR_CRYPTO_FIPS_UNAVAILABLE`
An attempt was made to enable or disable FIPS mode, but FIPS mode was not
available.
<a id="ERR_CRYPTO_HASH_FINALIZED"></a>
### `ERR_CRYPTO_HASH_FINALIZED`
[`hash.digest()`][] was called multiple times. The `hash.digest()` method must
be called no more than one time per instance of a `Hash` object.
<a id="ERR_CRYPTO_HASH_UPDATE_FAILED"></a>
### `ERR_CRYPTO_HASH_UPDATE_FAILED`
[`hash.update()`][] failed for any reason. This should rarely, if ever, happen.
<a id="ERR_CRYPTO_INCOMPATIBLE_KEY_OPTIONS"></a>
### `ERR_CRYPTO_INCOMPATIBLE_KEY_OPTIONS`
The selected public or private key encoding is incompatible with other options.
<a id="ERR_CRYPTO_INVALID_DIGEST"></a>
### `ERR_CRYPTO_INVALID_DIGEST`
An invalid [crypto digest algorithm][] was specified.
<a id="ERR_CRYPTO_INVALID_KEY_OBJECT_TYPE"></a>
### `ERR_CRYPTO_INVALID_KEY_OBJECT_TYPE`
The given crypto key object's type is invalid for the attempted operation.
<a id="ERR_CRYPTO_INVALID_STATE"></a>
### `ERR_CRYPTO_INVALID_STATE`
A crypto method was used on an object that was in an invalid state. For
instance, calling [`cipher.getAuthTag()`][] before calling `cipher.final()`.
<a id="ERR_CRYPTO_PBKDF2_ERROR"></a>
### `ERR_CRYPTO_PBKDF2_ERROR`
The PBKDF2 algorithm failed for unspecified reasons. OpenSSL does not provide
more details and therefore neither does Node.js.
<a id="ERR_CRYPTO_SCRYPT_INVALID_PARAMETER"></a>
### `ERR_CRYPTO_SCRYPT_INVALID_PARAMETER`
One or more [`crypto.scrypt()`][] or [`crypto.scryptSync()`][] parameters are
outside their legal range.
<a id="ERR_CRYPTO_SCRYPT_NOT_SUPPORTED"></a>
### `ERR_CRYPTO_SCRYPT_NOT_SUPPORTED`
Node.js was compiled without `scrypt` support. Not possible with the official
release binaries but can happen with custom builds, including distro builds.
<a id="ERR_CRYPTO_SIGN_KEY_REQUIRED"></a>
### `ERR_CRYPTO_SIGN_KEY_REQUIRED`
A signing `key` was not provided to the [`sign.sign()`][] method.
<a id="ERR_CRYPTO_TIMING_SAFE_EQUAL_LENGTH"></a>
### `ERR_CRYPTO_TIMING_SAFE_EQUAL_LENGTH`
[`crypto.timingSafeEqual()`][] was called with `Buffer`, `TypedArray`, or
`DataView` arguments of different lengths.
<a id="ERR_DIR_CLOSED"></a>
### `ERR_DIR_CLOSED`
The [`fs.Dir`][] was previously closed.
<a id="ERR_DNS_SET_SERVERS_FAILED"></a>
### `ERR_DNS_SET_SERVERS_FAILED`
`c-ares` failed to set the DNS server.
<a id="ERR_DOMAIN_CALLBACK_NOT_AVAILABLE"></a>
### `ERR_DOMAIN_CALLBACK_NOT_AVAILABLE`
The `domain` module was not usable since it could not establish the required
error handling hooks, because
[`process.setUncaughtExceptionCaptureCallback()`][] had been called at an
earlier point in time.
<a id="ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE"></a>
### `ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE`
[`process.setUncaughtExceptionCaptureCallback()`][] could not be called
because the `domain` module has been loaded at an earlier point in time.
The stack trace is extended to include the point in time at which the
`domain` module had been loaded.
<a id="ERR_ENCODING_INVALID_ENCODED_DATA"></a>
### `ERR_ENCODING_INVALID_ENCODED_DATA`
Data provided to `TextDecoder()` API was invalid according to the encoding
provided.
<a id="ERR_ENCODING_NOT_SUPPORTED"></a>
### `ERR_ENCODING_NOT_SUPPORTED`
Encoding provided to `TextDecoder()` API was not one of the
[WHATWG Supported Encodings][].
<a id="ERR_FALSY_VALUE_REJECTION"></a>
### `ERR_FALSY_VALUE_REJECTION`
A `Promise` that was callbackified via `util.callbackify()` was rejected with a
falsy value.
<a id="ERR_FS_FILE_TOO_LARGE"></a>
### `ERR_FS_FILE_TOO_LARGE`
An attempt has been made to read a file whose size is larger than the maximum
allowed size for a `Buffer`.
<a id="ERR_FS_INVALID_SYMLINK_TYPE"></a>
### `ERR_FS_INVALID_SYMLINK_TYPE`
An invalid symlink type was passed to the [`fs.symlink()`][] or
[`fs.symlinkSync()`][] methods.
<a id="ERR_HTTP_HEADERS_SENT"></a>
### `ERR_HTTP_HEADERS_SENT`
An attempt was made to add more headers after the headers had already been sent.
<a id="ERR_HTTP_INVALID_HEADER_VALUE"></a>
### `ERR_HTTP_INVALID_HEADER_VALUE`
An invalid HTTP header value was specified.
<a id="ERR_HTTP_INVALID_STATUS_CODE"></a>
### `ERR_HTTP_INVALID_STATUS_CODE`
Status code was outside the regular status code range (100-999).
<a id="ERR_HTTP_TRAILER_INVALID"></a>
### `ERR_HTTP_TRAILER_INVALID`
The `Trailer` header was set even though the transfer encoding does not support
that.
<a id="ERR_HTTP2_ALTSVC_INVALID_ORIGIN"></a>
### `ERR_HTTP2_ALTSVC_INVALID_ORIGIN`
HTTP/2 ALTSVC frames require a valid origin.
<a id="ERR_HTTP2_ALTSVC_LENGTH"></a>
### `ERR_HTTP2_ALTSVC_LENGTH`
HTTP/2 ALTSVC frames are limited to a maximum of 16,382 payload bytes.
<a id="ERR_HTTP2_CONNECT_AUTHORITY"></a>
### `ERR_HTTP2_CONNECT_AUTHORITY`
For HTTP/2 requests using the `CONNECT` method, the `:authority` pseudo-header
is required.
<a id="ERR_HTTP2_CONNECT_PATH"></a>
### `ERR_HTTP2_CONNECT_PATH`
For HTTP/2 requests using the `CONNECT` method, the `:path` pseudo-header is
forbidden.
<a id="ERR_HTTP2_CONNECT_SCHEME"></a>
### `ERR_HTTP2_CONNECT_SCHEME`
For HTTP/2 requests using the `CONNECT` method, the `:scheme` pseudo-header is
forbidden.
<a id="ERR_HTTP2_ERROR"></a>
### `ERR_HTTP2_ERROR`
A non-specific HTTP/2 error has occurred.
<a id="ERR_HTTP2_GOAWAY_SESSION"></a>
### `ERR_HTTP2_GOAWAY_SESSION`
New HTTP/2 Streams may not be opened after the `Http2Session` has received a
`GOAWAY` frame from the connected peer.
<a id="ERR_HTTP2_HEADERS_AFTER_RESPOND"></a>
### `ERR_HTTP2_HEADERS_AFTER_RESPOND`
An additional headers was specified after an HTTP/2 response was initiated.
<a id="ERR_HTTP2_HEADERS_SENT"></a>
### `ERR_HTTP2_HEADERS_SENT`
An attempt was made to send multiple response headers.
<a id="ERR_HTTP2_HEADER_SINGLE_VALUE"></a>
### `ERR_HTTP2_HEADER_SINGLE_VALUE`
Multiple values were provided for an HTTP/2 header field that was required to
have only a single value.
<a id="ERR_HTTP2_INFO_STATUS_NOT_ALLOWED"></a>
### `ERR_HTTP2_INFO_STATUS_NOT_ALLOWED`
Informational HTTP status codes (`1xx`) may not be set as the response status
code on HTTP/2 responses.
<a id="ERR_HTTP2_INVALID_CONNECTION_HEADERS"></a>
### `ERR_HTTP2_INVALID_CONNECTION_HEADERS`
HTTP/1 connection specific headers are forbidden to be used in HTTP/2
requests and responses.
<a id="ERR_HTTP2_INVALID_HEADER_VALUE"></a>
### `ERR_HTTP2_INVALID_HEADER_VALUE`
An invalid HTTP/2 header value was specified.
<a id="ERR_HTTP2_INVALID_INFO_STATUS"></a>
### `ERR_HTTP2_INVALID_INFO_STATUS`
An invalid HTTP informational status code has been specified. Informational
status codes must be an integer between `100` and `199` (inclusive).
<a id="ERR_HTTP2_INVALID_ORIGIN"></a>
### `ERR_HTTP2_INVALID_ORIGIN`
HTTP/2 `ORIGIN` frames require a valid origin.
<a id="ERR_HTTP2_INVALID_PACKED_SETTINGS_LENGTH"></a>
### `ERR_HTTP2_INVALID_PACKED_SETTINGS_LENGTH`
Input `Buffer` and `Uint8Array` instances passed to the
`http2.getUnpackedSettings()` API must have a length that is a multiple of
six.
<a id="ERR_HTTP2_INVALID_PSEUDOHEADER"></a>
### `ERR_HTTP2_INVALID_PSEUDOHEADER`
Only valid HTTP/2 pseudoheaders (`:status`, `:path`, `:authority`, `:scheme`,
and `:method`) may be used.
<a id="ERR_HTTP2_INVALID_SESSION"></a>
### `ERR_HTTP2_INVALID_SESSION`
An action was performed on an `Http2Session` object that had already been
destroyed.
<a id="ERR_HTTP2_INVALID_SETTING_VALUE"></a>
### `ERR_HTTP2_INVALID_SETTING_VALUE`
An invalid value has been specified for an HTTP/2 setting.
<a id="ERR_HTTP2_INVALID_STREAM"></a>
### `ERR_HTTP2_INVALID_STREAM`
An operation was performed on a stream that had already been destroyed.
<a id="ERR_HTTP2_MAX_PENDING_SETTINGS_ACK"></a>
### `ERR_HTTP2_MAX_PENDING_SETTINGS_ACK`
Whenever an HTTP/2 `SETTINGS` frame is sent to a connected peer, the peer is
required to send an acknowledgment that it has received and applied the new
`SETTINGS`. By default, a maximum number of unacknowledged `SETTINGS` frames may
be sent at any given time. This error code is used when that limit has been
reached.
<a id="ERR_HTTP2_NESTED_PUSH"></a>
### `ERR_HTTP2_NESTED_PUSH`
An attempt was made to initiate a new push stream from within a push stream.
Nested push streams are not permitted.
<a id="ERR_HTTP2_NO_SOCKET_MANIPULATION"></a>
### `ERR_HTTP2_NO_SOCKET_MANIPULATION`
An attempt was made to directly manipulate (read, write, pause, resume, etc.) a
socket attached to an `Http2Session`.
<a id="ERR_HTTP2_ORIGIN_LENGTH"></a>
### `ERR_HTTP2_ORIGIN_LENGTH`
HTTP/2 `ORIGIN` frames are limited to a length of 16382 bytes.
<a id="ERR_HTTP2_OUT_OF_STREAMS"></a>
### `ERR_HTTP2_OUT_OF_STREAMS`
The number of streams created on a single HTTP/2 session reached the maximum
limit.
<a id="ERR_HTTP2_PAYLOAD_FORBIDDEN"></a>
### `ERR_HTTP2_PAYLOAD_FORBIDDEN`
A message payload was specified for an HTTP response code for which a payload is
forbidden.
<a id="ERR_HTTP2_PING_CANCEL"></a>
### `ERR_HTTP2_PING_CANCEL`
An HTTP/2 ping was canceled.
<a id="ERR_HTTP2_PING_LENGTH"></a>
### `ERR_HTTP2_PING_LENGTH`
HTTP/2 ping payloads must be exactly 8 bytes in length.
<a id="ERR_HTTP2_PSEUDOHEADER_NOT_ALLOWED"></a>
### `ERR_HTTP2_PSEUDOHEADER_NOT_ALLOWED`
An HTTP/2 pseudo-header has been used inappropriately. Pseudo-headers are header
key names that begin with the `:` prefix.
<a id="ERR_HTTP2_PUSH_DISABLED"></a>
### `ERR_HTTP2_PUSH_DISABLED`
An attempt was made to create a push stream, which had been disabled by the
client.
<a id="ERR_HTTP2_SEND_FILE"></a>
### `ERR_HTTP2_SEND_FILE`
An attempt was made to use the `Http2Stream.prototype.responseWithFile()` API to
send a directory.
<a id="ERR_HTTP2_SEND_FILE_NOSEEK"></a>
### `ERR_HTTP2_SEND_FILE_NOSEEK`
An attempt was made to use the `Http2Stream.prototype.responseWithFile()` API to
send something other than a regular file, but `offset` or `length` options were
provided.
<a id="ERR_HTTP2_SESSION_ERROR"></a>
### `ERR_HTTP2_SESSION_ERROR`
The `Http2Session` closed with a non-zero error code.
<a id="ERR_HTTP2_SETTINGS_CANCEL"></a>
### `ERR_HTTP2_SETTINGS_CANCEL`
The `Http2Session` settings canceled.
<a id="ERR_HTTP2_SOCKET_BOUND"></a>
### `ERR_HTTP2_SOCKET_BOUND`
An attempt was made to connect a `Http2Session` object to a `net.Socket` or
`tls.TLSSocket` that had already been bound to another `Http2Session` object.
<a id="ERR_HTTP2_SOCKET_UNBOUND"></a>
### `ERR_HTTP2_SOCKET_UNBOUND`
An attempt was made to use the `socket` property of an `Http2Session` that
has already been closed.
<a id="ERR_HTTP2_STATUS_101"></a>
### `ERR_HTTP2_STATUS_101`
Use of the `101` Informational status code is forbidden in HTTP/2.
<a id="ERR_HTTP2_STATUS_INVALID"></a>
### `ERR_HTTP2_STATUS_INVALID`
An invalid HTTP status code has been specified. Status codes must be an integer
between `100` and `599` (inclusive).
<a id="ERR_HTTP2_STREAM_CANCEL"></a>
### `ERR_HTTP2_STREAM_CANCEL`
An `Http2Stream` was destroyed before any data was transmitted to the connected
peer.
<a id="ERR_HTTP2_STREAM_ERROR"></a>
### `ERR_HTTP2_STREAM_ERROR`
A non-zero error code was been specified in an `RST_STREAM` frame.
<a id="ERR_HTTP2_STREAM_SELF_DEPENDENCY"></a>
### `ERR_HTTP2_STREAM_SELF_DEPENDENCY`
When setting the priority for an HTTP/2 stream, the stream may be marked as
a dependency for a parent stream. This error code is used when an attempt is
made to mark a stream and dependent of itself.
<a id="ERR_HTTP2_TRAILERS_ALREADY_SENT"></a>
### `ERR_HTTP2_TRAILERS_ALREADY_SENT`
Trailing headers have already been sent on the `Http2Stream`.
<a id="ERR_HTTP2_TRAILERS_NOT_READY"></a>
### `ERR_HTTP2_TRAILERS_NOT_READY`
The `http2stream.sendTrailers()` method cannot be called until after the
`'wantTrailers'` event is emitted on an `Http2Stream` object. The
`'wantTrailers'` event will only be emitted if the `waitForTrailers` option
is set for the `Http2Stream`.
<a id="ERR_HTTP2_UNSUPPORTED_PROTOCOL"></a>
### `ERR_HTTP2_UNSUPPORTED_PROTOCOL`
`http2.connect()` was passed a URL that uses any protocol other than `http:` or
`https:`.
<a id="ERR_INTERNAL_ASSERTION"></a>
### `ERR_INTERNAL_ASSERTION`
There was a bug in Node.js or incorrect usage of Node.js internals.
To fix the error, open an issue at https://github.com/nodejs/node/issues.
<a id="ERR_INCOMPATIBLE_OPTION_PAIR"></a>
### `ERR_INCOMPATIBLE_OPTION_PAIR`
An option pair is incompatible with each other and can not be used at the same
time.
<a id="ERR_INPUT_TYPE_NOT_ALLOWED"></a>
### `ERR_INPUT_TYPE_NOT_ALLOWED`
> Stability: 1 - Experimental
The `--input-type` flag was used to attempt to execute a file. This flag can
only be used with input via `--eval`, `--print` or `STDIN`.
<a id="ERR_INSPECTOR_ALREADY_CONNECTED"></a>
### `ERR_INSPECTOR_ALREADY_CONNECTED`
While using the `inspector` module, an attempt was made to connect when the
inspector was already connected.
<a id="ERR_INSPECTOR_CLOSED"></a>
### `ERR_INSPECTOR_CLOSED`
While using the `inspector` module, an attempt was made to use the inspector
after the session had already closed.
<a id="ERR_INSPECTOR_COMMAND"></a>
### `ERR_INSPECTOR_COMMAND`
An error occurred while issuing a command via the `inspector` module.
<a id="ERR_INSPECTOR_NOT_ACTIVE"></a>
### `ERR_INSPECTOR_NOT_ACTIVE`
The `inspector` is not active when `inspector.waitForDebugger()` is called.
<a id="ERR_INSPECTOR_NOT_AVAILABLE"></a>
### `ERR_INSPECTOR_NOT_AVAILABLE`
The `inspector` module is not available for use.
<a id="ERR_INSPECTOR_NOT_CONNECTED"></a>
### `ERR_INSPECTOR_NOT_CONNECTED`
While using the `inspector` module, an attempt was made to use the inspector
before it was connected.
<a id="ERR_INSPECTOR_NOT_WORKER"></a>
### `ERR_INSPECTOR_NOT_WORKER`
An API was called on the main thread that can only be used from
the worker thread.
<a id="ERR_INVALID_ADDRESS_FAMILY"></a>
### `ERR_INVALID_ADDRESS_FAMILY`
The provided address family is not understood by the Node.js API.
<a id="ERR_INVALID_ARG_TYPE"></a>
### `ERR_INVALID_ARG_TYPE`
An argument of the wrong type was passed to a Node.js API.
<a id="ERR_INVALID_ARG_VALUE"></a>
### `ERR_INVALID_ARG_VALUE`
An invalid or unsupported value was passed for a given argument.
<a id="ERR_INVALID_ASYNC_ID"></a>
### `ERR_INVALID_ASYNC_ID`
An invalid `asyncId` or `triggerAsyncId` was passed using `AsyncHooks`. An id
less than -1 should never happen.
<a id="ERR_INVALID_BUFFER_SIZE"></a>
### `ERR_INVALID_BUFFER_SIZE`
A swap was performed on a `Buffer` but its size was not compatible with the
operation.
<a id="ERR_INVALID_CALLBACK"></a>
### `ERR_INVALID_CALLBACK`
A callback function was required but was not been provided to a Node.js API.
<a id="ERR_INVALID_CHAR"></a>
### `ERR_INVALID_CHAR`
Invalid characters were detected in headers.
<a id="ERR_INVALID_CURSOR_POS"></a>
### `ERR_INVALID_CURSOR_POS`
A cursor on a given stream cannot be moved to a specified row without a
specified column.
<a id="ERR_INVALID_FD"></a>
### `ERR_INVALID_FD`
A file descriptor ('fd') was not valid (e.g. it was a negative value).
<a id="ERR_INVALID_FD_TYPE"></a>
### `ERR_INVALID_FD_TYPE`
A file descriptor ('fd') type was not valid.
<a id="ERR_INVALID_FILE_URL_HOST"></a>
### `ERR_INVALID_FILE_URL_HOST`
A Node.js API that consumes `file:` URLs (such as certain functions in the
[`fs`][] module) encountered a file URL with an incompatible host. This
situation can only occur on Unix-like systems where only `localhost` or an empty
host is supported.
<a id="ERR_INVALID_FILE_URL_PATH"></a>
### `ERR_INVALID_FILE_URL_PATH`
A Node.js API that consumes `file:` URLs (such as certain functions in the
[`fs`][] module) encountered a file URL with an incompatible path. The exact
semantics for determining whether a path can be used is platform-dependent.
<a id="ERR_INVALID_HANDLE_TYPE"></a>
### `ERR_INVALID_HANDLE_TYPE`
An attempt was made to send an unsupported "handle" over an IPC communication
channel to a child process. See [`subprocess.send()`][] and [`process.send()`][]
for more information.
<a id="ERR_INVALID_HTTP_TOKEN"></a>
### `ERR_INVALID_HTTP_TOKEN`
An invalid HTTP token was supplied.
<a id="ERR_INVALID_IP_ADDRESS"></a>
### `ERR_INVALID_IP_ADDRESS`
An IP address is not valid.
<a id="ERR_INVALID_OPT_VALUE"></a>
### `ERR_INVALID_OPT_VALUE`
An invalid or unexpected value was passed in an options object.
<a id="ERR_INVALID_OPT_VALUE_ENCODING"></a>
### `ERR_INVALID_OPT_VALUE_ENCODING`
An invalid or unknown file encoding was passed.
<a id="ERR_INVALID_PACKAGE_CONFIG"></a>
### `ERR_INVALID_PACKAGE_CONFIG`
An invalid `package.json` file was found which failed parsing.
<a id="ERR_INVALID_PERFORMANCE_MARK"></a>
### `ERR_INVALID_PERFORMANCE_MARK`
While using the Performance Timing API (`perf_hooks`), a performance mark is
invalid.
<a id="ERR_INVALID_PROTOCOL"></a>
### `ERR_INVALID_PROTOCOL`
An invalid `options.protocol` was passed to `http.request()`.
<a id="ERR_INVALID_REPL_EVAL_CONFIG"></a>
### `ERR_INVALID_REPL_EVAL_CONFIG`
Both `breakEvalOnSigint` and `eval` options were set in the [`REPL`][] config,
which is not supported.
<a id="ERR_INVALID_REPL_INPUT"></a>
### `ERR_INVALID_REPL_INPUT`
The input may not be used in the [`REPL`][]. All prohibited inputs are
documented in the [`REPL`][]'s documentation.
<a id="ERR_INVALID_RETURN_PROPERTY"></a>
### `ERR_INVALID_RETURN_PROPERTY`
Thrown in case a function option does not provide a valid value for one of its
returned object properties on execution.
<a id="ERR_INVALID_RETURN_PROPERTY_VALUE"></a>
### `ERR_INVALID_RETURN_PROPERTY_VALUE`
Thrown in case a function option does not provide an expected value
type for one of its returned object properties on execution.
<a id="ERR_INVALID_RETURN_VALUE"></a>
### `ERR_INVALID_RETURN_VALUE`
Thrown in case a function option does not return an expected value
type on execution, such as when a function is expected to return a promise.
<a id="ERR_INVALID_SYNC_FORK_INPUT"></a>
### `ERR_INVALID_SYNC_FORK_INPUT`
A `Buffer`, `TypedArray`, `DataView` or `string` was provided as stdio input to
an asynchronous fork. See the documentation for the [`child_process`][] module
for more information.
<a id="ERR_INVALID_THIS"></a>
### `ERR_INVALID_THIS`
A Node.js API function was called with an incompatible `this` value.
```js
const urlSearchParams = new URLSearchParams('foo=bar&baz=new');
const buf = Buffer.alloc(1);
urlSearchParams.has.call(buf, 'foo');
// Throws a TypeError with code 'ERR_INVALID_THIS'
```
<a id="ERR_INVALID_TRANSFER_OBJECT"></a>
### `ERR_INVALID_TRANSFER_OBJECT`
An invalid transfer object was passed to `postMessage()`.
<a id="ERR_INVALID_TUPLE"></a>
### `ERR_INVALID_TUPLE`
An element in the `iterable` provided to the [WHATWG][WHATWG URL API]
[`URLSearchParams` constructor][`new URLSearchParams(iterable)`] did not
represent a `[name, value]` tuple – that is, if an element is not iterable, or
does not consist of exactly two elements.
<a id="ERR_INVALID_URI"></a>
### `ERR_INVALID_URI`
An invalid URI was passed.
<a id="ERR_INVALID_URL"></a>
### `ERR_INVALID_URL`
An invalid URL was passed to the [WHATWG][WHATWG URL API]
[`URL` constructor][`new URL(input)`] to be parsed. The thrown error object
typically has an additional property `'input'` that contains the URL that failed
to parse.
<a id="ERR_INVALID_URL_SCHEME"></a>
### `ERR_INVALID_URL_SCHEME`
An attempt was made to use a URL of an incompatible scheme (protocol) for a
specific purpose. It is only used in the [WHATWG URL API][] support in the
[`fs`][] module (which only accepts URLs with `'file'` scheme), but may be used
in other Node.js APIs as well in the future.
<a id="ERR_IPC_CHANNEL_CLOSED"></a>
### `ERR_IPC_CHANNEL_CLOSED`
An attempt was made to use an IPC communication channel that was already closed.
<a id="ERR_IPC_DISCONNECTED"></a>
### `ERR_IPC_DISCONNECTED`
An attempt was made to disconnect an IPC communication channel that was already
disconnected. See the documentation for the [`child_process`][] module
for more information.
<a id="ERR_IPC_ONE_PIPE"></a>
### `ERR_IPC_ONE_PIPE`
An attempt was made to create a child Node.js process using more than one IPC
communication channel. See the documentation for the [`child_process`][] module
for more information.
<a id="ERR_IPC_SYNC_FORK"></a>
### `ERR_IPC_SYNC_FORK`
An attempt was made to open an IPC communication channel with a synchronously
forked Node.js process. See the documentation for the [`child_process`][] module
for more information.
<a id="ERR_MANIFEST_ASSERT_INTEGRITY"></a>
### `ERR_MANIFEST_ASSERT_INTEGRITY`
An attempt was made to load a resource, but the resource did not match the
integrity defined by the policy manifest. See the documentation for [policy][]
manifests for more information.
<a id="ERR_MANIFEST_DEPENDENCY_MISSING"></a>
### `ERR_MANIFEST_DEPENDENCY_MISSING`
An attempt was made to load a resource, but the resource was not listed as a
dependency from the location that attempted to load it. See the documentation
for [policy][] manifests for more information.
<a id="ERR_MANIFEST_INTEGRITY_MISMATCH"></a>
### `ERR_MANIFEST_INTEGRITY_MISMATCH`
An attempt was made to load a policy manifest, but the manifest had multiple
entries for a resource which did not match each other. Update the manifest
entries to match in order to resolve this error. See the documentation for
[policy][] manifests for more information.
<a id="ERR_MANIFEST_INVALID_RESOURCE_FIELD"></a>
### `ERR_MANIFEST_INVALID_RESOURCE_FIELD`
A policy manifest resource had an invalid value for one of its fields. Update
the manifest entry to match in order to resolve this error. See the
documentation for [policy][] manifests for more information.
<a id="ERR_MANIFEST_PARSE_POLICY"></a>
### `ERR_MANIFEST_PARSE_POLICY`
An attempt was made to load a policy manifest, but the manifest was unable to
be parsed. See the documentation for [policy][] manifests for more information.
<a id="ERR_MANIFEST_TDZ"></a>
### `ERR_MANIFEST_TDZ`
An attempt was made to read from a policy manifest, but the manifest
initialization has not yet taken place. This is likely a bug in Node.js.
<a id="ERR_MANIFEST_UNKNOWN_ONERROR"></a>
### `ERR_MANIFEST_UNKNOWN_ONERROR`
A policy manifest was loaded, but had an unknown value for its "onerror"
behavior. See the documentation for [policy][] manifests for more information.
<a id="ERR_MEMORY_ALLOCATION_FAILED"></a>
### `ERR_MEMORY_ALLOCATION_FAILED`
An attempt was made to allocate memory (usually in the C++ layer) but it
failed.
<a id="ERR_METHOD_NOT_IMPLEMENTED"></a>
### `ERR_METHOD_NOT_IMPLEMENTED`
A method is required but not implemented.
<a id="ERR_MISSING_ARGS"></a>
### `ERR_MISSING_ARGS`
A required argument of a Node.js API was not passed. This is only used for
strict compliance with the API specification (which in some cases may accept
`func(undefined)` but not `func()`). In most native Node.js APIs,
`func(undefined)` and `func()` are treated identically, and the
[`ERR_INVALID_ARG_TYPE`][] error code may be used instead.
<a id="ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK"></a>
### `ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK`
> Stability: 1 - Experimental
An [ES Module][] loader hook specified `format: 'dynamic'` but did not provide
a `dynamicInstantiate` hook.
<a id="ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST"></a>
### `ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST`
A `MessagePort` was found in the object passed to a `postMessage()` call,
but not provided in the `transferList` for that call.
<a id="ERR_MISSING_PASSPHRASE"></a>
### `ERR_MISSING_PASSPHRASE`
An attempt was made to read an encrypted key without specifying a passphrase.
<a id="ERR_MISSING_PLATFORM_FOR_WORKER"></a>
### `ERR_MISSING_PLATFORM_FOR_WORKER`
The V8 platform used by this instance of Node.js does not support creating
Workers. This is caused by lack of embedder support for Workers. In particular,
this error will not occur with standard builds of Node.js.
<a id="ERR_MODULE_NOT_FOUND"></a>
### `ERR_MODULE_NOT_FOUND`
> Stability: 1 - Experimental
An [ES Module][] could not be resolved.
<a id="ERR_MULTIPLE_CALLBACK"></a>
### `ERR_MULTIPLE_CALLBACK`
A callback was called more than once.
A callback is almost always meant to only be called once as the query
can either be fulfilled or rejected but not both at the same time. The latter
would be possible by calling a callback more than once.
<a id="ERR_NAPI_CONS_FUNCTION"></a>
### `ERR_NAPI_CONS_FUNCTION`
While using `N-API`, a constructor passed was not a function.
<a id="ERR_NAPI_INVALID_DATAVIEW_ARGS"></a>
### `ERR_NAPI_INVALID_DATAVIEW_ARGS`
While calling `napi_create_dataview()`, a given `offset` was outside the bounds
of the dataview or `offset + length` was larger than a length of given `buffer`.
<a id="ERR_NAPI_INVALID_TYPEDARRAY_ALIGNMENT"></a>
### `ERR_NAPI_INVALID_TYPEDARRAY_ALIGNMENT`
While calling `napi_create_typedarray()`, the provided `offset` was not a
multiple of the element size.
<a id="ERR_NAPI_INVALID_TYPEDARRAY_LENGTH"></a>
### `ERR_NAPI_INVALID_TYPEDARRAY_LENGTH`
While calling `napi_create_typedarray()`, `(length * size_of_element) +
byte_offset` was larger than the length of given `buffer`.
<a id="ERR_NAPI_TSFN_CALL_JS"></a>
### `ERR_NAPI_TSFN_CALL_JS`
An error occurred while invoking the JavaScript portion of the thread-safe
function.
<a id="ERR_NAPI_TSFN_GET_UNDEFINED"></a>
### `ERR_NAPI_TSFN_GET_UNDEFINED`
An error occurred while attempting to retrieve the JavaScript `undefined`
value.
<a id="ERR_NAPI_TSFN_START_IDLE_LOOP"></a>
### `ERR_NAPI_TSFN_START_IDLE_LOOP`
On the main thread, values are removed from the queue associated with the
thread-safe function in an idle loop. This error indicates that an error
has occurred when attempting to start the loop.
<a id="ERR_NAPI_TSFN_STOP_IDLE_LOOP"></a>
### `ERR_NAPI_TSFN_STOP_IDLE_LOOP`
Once no more items are left in the queue, the idle loop must be suspended. This
error indicates that the idle loop has failed to stop.
<a id="ERR_NO_CRYPTO"></a>
### `ERR_NO_CRYPTO`
An attempt was made to use crypto features while Node.js was not compiled with
OpenSSL crypto support.
<a id="ERR_NO_ICU"></a>
### `ERR_NO_ICU`
An attempt was made to use features that require [ICU][], but Node.js was not
compiled with ICU support.
<a id="ERR_NON_CONTEXT_AWARE_DISABLED"></a>
### `ERR_NON_CONTEXT_AWARE_DISABLED`
A non-context-aware native addon was loaded in a process that disallows them.
<a id="ERR_OUT_OF_RANGE"></a>
### `ERR_OUT_OF_RANGE`
A given value is out of the accepted range.
<a id="ERR_REQUIRE_ESM"></a>
### `ERR_REQUIRE_ESM`
> Stability: 1 - Experimental
An attempt was made to `require()` an [ES Module][].
<a id="ERR_SCRIPT_EXECUTION_INTERRUPTED"></a>
### `ERR_SCRIPT_EXECUTION_INTERRUPTED`
Script execution was interrupted by `SIGINT` (For example, when Ctrl+C was
pressed).
<a id="ERR_SCRIPT_EXECUTION_TIMEOUT"></a>
### `ERR_SCRIPT_EXECUTION_TIMEOUT`
Script execution timed out, possibly due to bugs in the script being executed.
<a id="ERR_SERVER_ALREADY_LISTEN"></a>
### `ERR_SERVER_ALREADY_LISTEN`
The [`server.listen()`][] method was called while a `net.Server` was already
listening. This applies to all instances of `net.Server`, including HTTP, HTTPS,
and HTTP/2 `Server` instances.
<a id="ERR_SERVER_NOT_RUNNING"></a>
### `ERR_SERVER_NOT_RUNNING`
The [`server.close()`][] method was called when a `net.Server` was not
running. This applies to all instances of `net.Server`, including HTTP, HTTPS,
and HTTP/2 `Server` instances.
<a id="ERR_SOCKET_ALREADY_BOUND"></a>
### `ERR_SOCKET_ALREADY_BOUND`
An attempt was made to bind a socket that has already been bound.
<a id="ERR_SOCKET_BAD_BUFFER_SIZE"></a>
### `ERR_SOCKET_BAD_BUFFER_SIZE`
An invalid (negative) size was passed for either the `recvBufferSize` or
`sendBufferSize` options in [`dgram.createSocket()`][].
<a id="ERR_SOCKET_BAD_PORT"></a>
### `ERR_SOCKET_BAD_PORT`
An API function expecting a port >= 0 and < 65536 received an invalid value.
<a id="ERR_SOCKET_BAD_TYPE"></a>
### `ERR_SOCKET_BAD_TYPE`
An API function expecting a socket type (`udp4` or `udp6`) received an invalid
value.
<a id="ERR_SOCKET_BUFFER_SIZE"></a>
### `ERR_SOCKET_BUFFER_SIZE`
While using [`dgram.createSocket()`][], the size of the receive or send `Buffer`
could not be determined.
<a id="ERR_SOCKET_CANNOT_SEND"></a>
### `ERR_SOCKET_CANNOT_SEND`
Data could be sent on a socket.
<a id="ERR_SOCKET_CLOSED"></a>
### `ERR_SOCKET_CLOSED`
An attempt was made to operate on an already closed socket.
<a id="ERR_SOCKET_DGRAM_IS_CONNECTED"></a>
### `ERR_SOCKET_DGRAM_IS_CONNECTED`
A [`dgram.connect()`][] call was made on an already connected socket.
<a id="ERR_SOCKET_DGRAM_NOT_CONNECTED"></a>
### `ERR_SOCKET_DGRAM_NOT_CONNECTED`
A [`dgram.disconnect()`][] or [`dgram.remoteAddress()`][] call was made on a
disconnected socket.
<a id="ERR_SOCKET_DGRAM_NOT_RUNNING"></a>
### `ERR_SOCKET_DGRAM_NOT_RUNNING`
A call was made and the UDP subsystem was not running.
<a id="ERR_SRI_PARSE"></a>
### `ERR_SRI_PARSE`
A string was provided for a Subresource Integrity check, but was unable to be
parsed. Check the format of integrity attributes by looking at the
[Subresource Integrity specification][].
<a id="ERR_STREAM_CANNOT_PIPE"></a>
### `ERR_STREAM_CANNOT_PIPE`
An attempt was made to call [`stream.pipe()`][] on a [`Writable`][] stream.
<a id="ERR_STREAM_DESTROYED"></a>
### `ERR_STREAM_DESTROYED`
A stream method was called that cannot complete because the stream was
destroyed using `stream.destroy()`.
<a id="ERR_STREAM_ALREADY_FINISHED"></a>
### `ERR_STREAM_ALREADY_FINISHED`
A stream method was called that cannot complete because the stream was
finished.
<a id="ERR_STREAM_NULL_VALUES"></a>
### `ERR_STREAM_NULL_VALUES`
An attempt was made to call [`stream.write()`][] with a `null` chunk.
<a id="ERR_STREAM_PREMATURE_CLOSE"></a>
### `ERR_STREAM_PREMATURE_CLOSE`
An error returned by `stream.finished()` and `stream.pipeline()`, when a stream
or a pipeline ends non gracefully with no explicit error.
<a id="ERR_STREAM_PUSH_AFTER_EOF"></a>
### `ERR_STREAM_PUSH_AFTER_EOF`
An attempt was made to call [`stream.push()`][] after a `null`(EOF) had been
pushed to the stream.
<a id="ERR_STREAM_UNSHIFT_AFTER_END_EVENT"></a>
### `ERR_STREAM_UNSHIFT_AFTER_END_EVENT`
An attempt was made to call [`stream.unshift()`][] after the `'end'` event was
emitted.
<a id="ERR_STREAM_WRAP"></a>
### `ERR_STREAM_WRAP`
Prevents an abort if a string decoder was set on the Socket or if the decoder
is in `objectMode`.
```js
const Socket = require('net').Socket;
const instance = new Socket();
instance.setEncoding('utf8');
```
<a id="ERR_STREAM_WRITE_AFTER_END"></a>
### `ERR_STREAM_WRITE_AFTER_END`
An attempt was made to call [`stream.write()`][] after `stream.end()` has been
called.
<a id="ERR_STRING_TOO_LONG"></a>
### `ERR_STRING_TOO_LONG`
An attempt has been made to create a string longer than the maximum allowed
length.
<a id="ERR_SYNTHETIC"></a>
### `ERR_SYNTHETIC`
An artificial error object used to capture the call stack for diagnostic
reports.
<a id="ERR_SYSTEM_ERROR"></a>
### `ERR_SYSTEM_ERROR`
An unspecified or non-specific system error has occurred within the Node.js
process. The error object will have an `err.info` object property with
additional details.
<a id="ERR_TLS_CERT_ALTNAME_INVALID"></a>
### `ERR_TLS_CERT_ALTNAME_INVALID`
While using TLS, the hostname/IP of the peer did not match any of the
`subjectAltNames` in its certificate.
<a id="ERR_TLS_DH_PARAM_SIZE"></a>
### `ERR_TLS_DH_PARAM_SIZE`
While using TLS, the parameter offered for the Diffie-Hellman (`DH`)
key-agreement protocol is too small. By default, the key length must be greater
than or equal to 1024 bits to avoid vulnerabilities, even though it is strongly
recommended to use 2048 bits or larger for stronger security.
<a id="ERR_TLS_HANDSHAKE_TIMEOUT"></a>
### `ERR_TLS_HANDSHAKE_TIMEOUT`
A TLS/SSL handshake timed out. In this case, the server must also abort the
connection.
<a id="ERR_TLS_INVALID_CONTEXT">
### `ERR_TLS_INVALID_CONTEXT`
<!-- YAML
added: v13.3.0
-->
The context must be a `SecureContext`.
<a id="ERR_TLS_INVALID_PROTOCOL_METHOD"></a>
### `ERR_TLS_INVALID_PROTOCOL_METHOD`
The specified `secureProtocol` method is invalid. It is either unknown, or
disabled because it is insecure.
<a id="ERR_TLS_INVALID_PROTOCOL_VERSION"></a>
### `ERR_TLS_INVALID_PROTOCOL_VERSION`
Valid TLS protocol versions are `'TLSv1'`, `'TLSv1.1'`, or `'TLSv1.2'`.
<a id="ERR_TLS_PROTOCOL_VERSION_CONFLICT"></a>
### `ERR_TLS_PROTOCOL_VERSION_CONFLICT`
Attempting to set a TLS protocol `minVersion` or `maxVersion` conflicts with an
attempt to set the `secureProtocol` explicitly. Use one mechanism or the other.
<a id="ERR_TLS_RENEGOTIATION_DISABLED"></a>
### `ERR_TLS_RENEGOTIATION_DISABLED`
An attempt was made to renegotiate TLS on a socket instance with TLS disabled.
<a id="ERR_TLS_REQUIRED_SERVER_NAME"></a>
### `ERR_TLS_REQUIRED_SERVER_NAME`
While using TLS, the `server.addContext()` method was called without providing
a hostname in the first parameter.
<a id="ERR_TLS_SESSION_ATTACK"></a>
### `ERR_TLS_SESSION_ATTACK`
An excessive amount of TLS renegotiations is detected, which is a potential
vector for denial-of-service attacks.
<a id="ERR_TLS_SNI_FROM_SERVER"></a>
### `ERR_TLS_SNI_FROM_SERVER`
An attempt was made to issue Server Name Indication from a TLS server-side
socket, which is only valid from a client.
<a id="ERR_TLS_PSK_SET_IDENTIY_HINT_FAILED"></a>
### ERR_TLS_PSK_SET_IDENTIY_HINT_FAILED
Failed to set PSK identity hint. Hint may be too long.
<a id="ERR_TRACE_EVENTS_CATEGORY_REQUIRED"></a>
### `ERR_TRACE_EVENTS_CATEGORY_REQUIRED`
The `trace_events.createTracing()` method requires at least one trace event
category.
<a id="ERR_TRACE_EVENTS_UNAVAILABLE"></a>
### `ERR_TRACE_EVENTS_UNAVAILABLE`
The `trace_events` module could not be loaded because Node.js was compiled with
the `--without-v8-platform` flag.
<a id="ERR_TRANSFERRING_EXTERNALIZED_SHAREDARRAYBUFFER"></a>
### `ERR_TRANSFERRING_EXTERNALIZED_SHAREDARRAYBUFFER`
A `SharedArrayBuffer` whose memory is not managed by the JavaScript engine
or by Node.js was encountered during serialization. Such a `SharedArrayBuffer`
cannot be serialized.
This can only happen when native addons create `SharedArrayBuffer`s in
"externalized" mode, or put existing `SharedArrayBuffer` into externalized mode.
<a id="ERR_TRANSFORM_ALREADY_TRANSFORMING"></a>
### `ERR_TRANSFORM_ALREADY_TRANSFORMING`
A `Transform` stream finished while it was still transforming.
<a id="ERR_TRANSFORM_WITH_LENGTH_0"></a>
### `ERR_TRANSFORM_WITH_LENGTH_0`
A `Transform` stream finished with data still in the write buffer.
<a id="ERR_TTY_INIT_FAILED"></a>
### `ERR_TTY_INIT_FAILED`
The initialization of a TTY failed due to a system error.
<a id="ERR_UNCAUGHT_EXCEPTION_CAPTURE_ALREADY_SET"></a>
### `ERR_UNCAUGHT_EXCEPTION_CAPTURE_ALREADY_SET`
[`process.setUncaughtExceptionCaptureCallback()`][] was called twice,
without first resetting the callback to `null`.
This error is designed to prevent accidentally overwriting a callback registered
from another module.
<a id="ERR_UNESCAPED_CHARACTERS"></a>
### `ERR_UNESCAPED_CHARACTERS`
A string that contained unescaped characters was received.
<a id="ERR_UNHANDLED_ERROR"></a>
### `ERR_UNHANDLED_ERROR`
An unhandled error occurred (for instance, when an `'error'` event is emitted
by an [`EventEmitter`][] but an `'error'` handler is not registered).
<a id="ERR_UNKNOWN_BUILTIN_MODULE"></a>
### `ERR_UNKNOWN_BUILTIN_MODULE`
Used to identify a specific kind of internal Node.js error that should not
typically be triggered by user code. Instances of this error point to an
internal bug within the Node.js binary itself.
<a id="ERR_UNKNOWN_CREDENTIAL"></a>
### `ERR_UNKNOWN_CREDENTIAL`
A Unix group or user identifier that does not exist was passed.
<a id="ERR_UNKNOWN_ENCODING"></a>
### `ERR_UNKNOWN_ENCODING`
An invalid or unknown encoding option was passed to an API.
<a id="ERR_UNKNOWN_FILE_EXTENSION"></a>
### `ERR_UNKNOWN_FILE_EXTENSION`
> Stability: 1 - Experimental
An attempt was made to load a module with an unknown or unsupported file
extension.
<a id="ERR_UNKNOWN_MODULE_FORMAT"></a>
### `ERR_UNKNOWN_MODULE_FORMAT`
> Stability: 1 - Experimental
An attempt was made to load a module with an unknown or unsupported format.
<a id="ERR_UNKNOWN_SIGNAL"></a>
### `ERR_UNKNOWN_SIGNAL`
An invalid or unknown process signal was passed to an API expecting a valid
signal (such as [`subprocess.kill()`][]).
<a id="ERR_UNSUPPORTED_ESM_URL_SCHEME"></a>
### `ERR_UNSUPPORTED_ESM_URL_SCHEME`
`import` with URL schemes other than `file` and `data` is unsupported.
<a id="ERR_V8BREAKITERATOR"></a>
### `ERR_V8BREAKITERATOR`
The V8 `BreakIterator` API was used but the full ICU data set is not installed.
<a id="ERR_VALID_PERFORMANCE_ENTRY_TYPE"></a>
### `ERR_VALID_PERFORMANCE_ENTRY_TYPE`
While using the Performance Timing API (`perf_hooks`), no valid performance
entry types were found.
<a id="ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING"></a>
### `ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING`
A dynamic import callback was not specified.
<a id="ERR_VM_MODULE_ALREADY_LINKED"></a>
### `ERR_VM_MODULE_ALREADY_LINKED`
The module attempted to be linked is not eligible for linking, because of one of
the following reasons:
* It has already been linked (`linkingStatus` is `'linked'`)
* It is being linked (`linkingStatus` is `'linking'`)
* Linking has failed for this module (`linkingStatus` is `'errored'`)
<a id="ERR_VM_MODULE_DIFFERENT_CONTEXT"></a>
### `ERR_VM_MODULE_DIFFERENT_CONTEXT`
The module being returned from the linker function is from a different context
than the parent module. Linked modules must share the same context.
<a id="ERR_VM_MODULE_LINKING_ERRORED"></a>
### `ERR_VM_MODULE_LINKING_ERRORED`
The linker function returned a module for which linking has failed.
<a id="ERR_VM_MODULE_NOT_MODULE"></a>
### `ERR_VM_MODULE_NOT_MODULE`
The fulfilled value of a linking promise is not a `vm.Module` object.
<a id="ERR_VM_MODULE_STATUS"></a>
### `ERR_VM_MODULE_STATUS`
The current module's status does not allow for this operation. The specific
meaning of the error depends on the specific function.
<a id="ERR_WASI_ALREADY_STARTED"></a>
### `ERR_WASI_ALREADY_STARTED`
The WASI instance has already started.
<a id="ERR_WORKER_INVALID_EXEC_ARGV"></a>
### `ERR_WORKER_INVALID_EXEC_ARGV`
The `execArgv` option passed to the `Worker` constructor contains
invalid flags.
<a id="ERR_WORKER_OUT_OF_MEMORY"></a>
### `ERR_WORKER_OUT_OF_MEMORY`
The `Worker` instance terminated because it reached its memory limit.
<a id="ERR_WORKER_PATH"></a>
### `ERR_WORKER_PATH`
The path for the main script of a worker is neither an absolute path
nor a relative path starting with `./` or `../`.
<a id="ERR_WORKER_UNSERIALIZABLE_ERROR"></a>
### `ERR_WORKER_UNSERIALIZABLE_ERROR`
All attempts at serializing an uncaught exception from a worker thread failed.
<a id="ERR_WORKER_UNSUPPORTED_EXTENSION"></a>
### `ERR_WORKER_UNSUPPORTED_EXTENSION`
The pathname used for the main script of a worker has an
unknown file extension.
<a id="ERR_WORKER_UNSUPPORTED_OPERATION"></a>
### `ERR_WORKER_UNSUPPORTED_OPERATION`
The requested functionality is not supported in worker threads.
<a id="ERR_ZLIB_INITIALIZATION_FAILED"></a>
### `ERR_ZLIB_INITIALIZATION_FAILED`
Creation of a [`zlib`][] object failed due to incorrect configuration.
<a id="HPE_HEADER_OVERFLOW"></a>
### `HPE_HEADER_OVERFLOW`
<!-- YAML
changes:
- version: v11.4.0
pr-url: https://github.com/nodejs/node/commit/186035243fad247e3955f
description: Max header size in `http_parser` was set to 8KB.
-->
Too much HTTP header data was received. In order to protect against malicious or
malconfigured clients, if more than 8KB of HTTP header data is received then
HTTP parsing will abort without a request or response object being created, and
an `Error` with this code will be emitted.
<a id="MODULE_NOT_FOUND"></a>
### `MODULE_NOT_FOUND`
<!-- YAML
changes:
- version: v12.0.0
pr-url: https://github.com/nodejs/node/pull/25690
description: Added `requireStack` property.
-->
A module file could not be resolved while attempting a [`require()`][] or
`import` operation.
## Legacy Node.js Error Codes
> Stability: 0 - Deprecated. These error codes are either inconsistent, or have
> been removed.
<a id="ERR_CANNOT_TRANSFER_OBJECT"></a>
### `ERR_CANNOT_TRANSFER_OBJECT`
<!--
added: v10.5.0
removed: v12.5.0
-->
The value passed to `postMessage()` contained an object that is not supported
for transferring.
<a id="ERR_CLOSED_MESSAGE_PORT"></a>
### `ERR_CLOSED_MESSAGE_PORT`
<!-- YAML
added: v10.5.0
removed: v11.12.0
-->
There was an attempt to use a `MessagePort` instance in a closed
state, usually after `.close()` has been called.
<a id="ERR_CRYPTO_HASH_DIGEST_NO_UTF16"></a>
### `ERR_CRYPTO_HASH_DIGEST_NO_UTF16`
<!-- YAML
added: v9.0.0
removed: v12.12.0
-->
The UTF-16 encoding was used with [`hash.digest()`][]. While the
`hash.digest()` method does allow an `encoding` argument to be passed in,
causing the method to return a string rather than a `Buffer`, the UTF-16
encoding (e.g. `ucs` or `utf16le`) is not supported.
<a id="ERR_HTTP2_FRAME_ERROR"></a>
### `ERR_HTTP2_FRAME_ERROR`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used when a failure occurs sending an individual frame on the HTTP/2
session.
<a id="ERR_HTTP2_HEADERS_OBJECT"></a>
### `ERR_HTTP2_HEADERS_OBJECT`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used when an HTTP/2 Headers Object is expected.
<a id="ERR_HTTP2_HEADER_REQUIRED"></a>
### `ERR_HTTP2_HEADER_REQUIRED`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used when a required header is missing in an HTTP/2 message.
<a id="ERR_HTTP2_INFO_HEADERS_AFTER_RESPOND"></a>
### `ERR_HTTP2_INFO_HEADERS_AFTER_RESPOND`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
HTTP/2 informational headers must only be sent *prior* to calling the
`Http2Stream.prototype.respond()` method.
<a id="ERR_HTTP2_STREAM_CLOSED"></a>
### `ERR_HTTP2_STREAM_CLOSED`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used when an action has been performed on an HTTP/2 Stream that has already
been closed.
<a id="ERR_HTTP_INVALID_CHAR"></a>
### `ERR_HTTP_INVALID_CHAR`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used when an invalid character is found in an HTTP response status message
(reason phrase).
<a id="ERR_INDEX_OUT_OF_RANGE"></a>
### `ERR_INDEX_OUT_OF_RANGE`
<!-- YAML
added: v10.0.0
removed: v11.0.0
-->
A given index was out of the accepted range (e.g. negative offsets).
<a id="ERR_NAPI_CONS_PROTOTYPE_OBJECT"></a>
### `ERR_NAPI_CONS_PROTOTYPE_OBJECT`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used by the `N-API` when `Constructor.prototype` is not an object.
<a id="ERR_NO_LONGER_SUPPORTED"></a>
### `ERR_NO_LONGER_SUPPORTED`
A Node.js API was called in an unsupported manner, such as
`Buffer.write(string, encoding, offset[, length])`.
<a id="ERR_OUTOFMEMORY"></a>
### `ERR_OUTOFMEMORY`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used generically to identify that an operation caused an out of memory
condition.
<a id="ERR_PARSE_HISTORY_DATA"></a>
### `ERR_PARSE_HISTORY_DATA`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
The `repl` module was unable to parse data from the REPL history file.
<a id="ERR_STDERR_CLOSE"></a>
### `ERR_STDERR_CLOSE`
<!-- YAML
removed: v10.12.0
changes:
- version: v10.12.0
pr-url: https://github.com/nodejs/node/pull/23053
description: Rather than emitting an error, `process.stderr.end()` now
only closes the stream side but not the underlying resource,
making this error obsolete.
-->
An attempt was made to close the `process.stderr` stream. By design, Node.js
does not allow `stdout` or `stderr` streams to be closed by user code.
<a id="ERR_STDOUT_CLOSE"></a>
### `ERR_STDOUT_CLOSE`
<!-- YAML
removed: v10.12.0
changes:
- version: v10.12.0
pr-url: https://github.com/nodejs/node/pull/23053
description: Rather than emitting an error, `process.stderr.end()` now
only closes the stream side but not the underlying resource,
making this error obsolete.
-->
An attempt was made to close the `process.stdout` stream. By design, Node.js
does not allow `stdout` or `stderr` streams to be closed by user code.
<a id="ERR_STREAM_READ_NOT_IMPLEMENTED"></a>
### `ERR_STREAM_READ_NOT_IMPLEMENTED`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used when an attempt is made to use a readable stream that has not implemented
[`readable._read()`][].
<a id="ERR_TLS_RENEGOTIATION_FAILED"></a>
### `ERR_TLS_RENEGOTIATION_FAILED`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used when a TLS renegotiation request has failed in a non-specific way.
<a id="ERR_UNKNOWN_BUILTIN_MODULE"></a>
### `ERR_UNKNOWN_BUILTIN_MODULE`
<!-- YAML
added: v8.0.0
removed: v9.0.0
-->
The `'ERR_UNKNOWN_BUILTIN_MODULE'` error code is used to identify a specific
kind of internal Node.js error that should not typically be triggered by user
code. Instances of this error point to an internal bug within the Node.js
binary itself.
<a id="ERR_UNKNOWN_STDIN_TYPE"></a>
### `ERR_UNKNOWN_STDIN_TYPE`
<!-- YAML
added: v8.0.0
removed: v11.7.0
-->
An attempt was made to launch a Node.js process with an unknown `stdin` file
type. This error is usually an indication of a bug within Node.js itself,
although it is possible for user code to trigger it.
<a id="ERR_UNKNOWN_STREAM_TYPE"></a>
### `ERR_UNKNOWN_STREAM_TYPE`
<!-- YAML
added: v8.0.0
removed: v11.7.0
-->
An attempt was made to launch a Node.js process with an unknown `stdout` or
`stderr` file type. This error is usually an indication of a bug within Node.js
itself, although it is possible for user code to trigger it.
<a id="ERR_VALUE_OUT_OF_RANGE"></a>
### `ERR_VALUE_OUT_OF_RANGE`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used when a given value is out of the accepted range.
<a id="ERR_VM_MODULE_NOT_LINKED"></a>
### `ERR_VM_MODULE_NOT_LINKED`
The module must be successfully linked before instantiation.
<a id="ERR_ZLIB_BINDING_CLOSED"></a>
### `ERR_ZLIB_BINDING_CLOSED`
<!-- YAML
added: v9.0.0
removed: v10.0.0
-->
Used when an attempt is made to use a `zlib` object after it has already been
closed.
### Other error codes
These errors have never been released, but had been present on master between
releases.
<a id="ERR_ENTRY_TYPE_MISMATCH"></a>
#### `ERR_ENTRY_TYPE_MISMATCH`
> Stability: 1 - Experimental
The `--entry-type=commonjs` flag was used to attempt to execute an `.mjs` file
or a `.js` file where the nearest parent `package.json` contains
`"type": "module"`; or
the `--entry-type=module` flag was used to attempt to execute a `.cjs` file or
a `.js` file where the nearest parent `package.json` either lacks a `"type"`
field or contains `"type": "commonjs"`.
<a id="ERR_FS_WATCHER_ALREADY_STARTED"></a>
#### `ERR_FS_WATCHER_ALREADY_STARTED`
An attempt was made to start a watcher returned by `fs.watch()` that has
already been started.
<a id="ERR_FS_WATCHER_NOT_STARTED"></a>
#### `ERR_FS_WATCHER_NOT_STARTED`
An attempt was made to initiate operations on a watcher returned by
`fs.watch()` that has not yet been started.
<a id="ERR_HTTP2_ALREADY_SHUTDOWN"></a>
#### `ERR_HTTP2_ALREADY_SHUTDOWN`
Occurs with multiple attempts to shutdown an HTTP/2 session.
<a id="ERR_HTTP2_ERROR"></a>
#### `ERR_HTTP2_ERROR`
A non-specific HTTP/2 error has occurred.
<a id="ERR_INVALID_REPL_HISTORY"></a>
#### `ERR_INVALID_REPL_HISTORY`
Used in the `repl` in case the old history file is used and an error occurred
while trying to read and parse it.
<a id="ERR_INVALID_REPL_TYPE"></a>
#### `ERR_INVALID_REPL_TYPE`
> Stability: 1 - Experimental
The `--entry-type=...` flag is not compatible with the Node.js REPL.
<a id="ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK"></a>
#### `ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK`
Used when an [ES Module][] loader hook specifies `format: 'dynamic'` but does
not provide a `dynamicInstantiate` hook.
<a id="ERR_STREAM_HAS_STRINGDECODER"></a>
#### `ERR_STREAM_HAS_STRINGDECODER`
Used to prevent an abort if a string decoder was set on the Socket.
```js
const Socket = require('net').Socket;
const instance = new Socket();
instance.setEncoding('utf8');
```
<a id="ERR_STRING_TOO_LARGE"></a>
#### `ERR_STRING_TOO_LARGE`
An attempt has been made to create a string larger than the maximum allowed
size.
<a id="ERR_TTY_WRITABLE_NOT_READABLE"></a>
#### `ERR_TTY_WRITABLE_NOT_READABLE`
This `Error` is thrown when a read is attempted on a TTY `WriteStream`,
such as `process.stdout.on('data')`.
[`'uncaughtException'`]: process.html#process_event_uncaughtexception
[`--force-fips`]: cli.html#cli_force_fips
[`Class: assert.AssertionError`]: assert.html#assert_class_assert_assertionerror
[`ERR_INVALID_ARG_TYPE`]: #ERR_INVALID_ARG_TYPE
[`EventEmitter`]: events.html#events_class_eventemitter
[`REPL`]: repl.html
[`Writable`]: stream.html#stream_class_stream_writable
[`child_process`]: child_process.html
[`cipher.getAuthTag()`]: crypto.html#crypto_cipher_getauthtag
[`crypto.scrypt()`]: crypto.html#crypto_crypto_scrypt_password_salt_keylen_options_callback
[`crypto.scryptSync()`]: crypto.html#crypto_crypto_scryptsync_password_salt_keylen_options
[`crypto.timingSafeEqual()`]: crypto.html#crypto_crypto_timingsafeequal_a_b
[`dgram.connect()`]: dgram.html#dgram_socket_connect_port_address_callback
[`dgram.createSocket()`]: dgram.html#dgram_dgram_createsocket_options_callback
[`dgram.disconnect()`]: dgram.html#dgram_socket_disconnect
[`dgram.remoteAddress()`]: dgram.html#dgram_socket_remoteaddress
[`errno`(3) man page]: http://man7.org/linux/man-pages/man3/errno.3.html
[`fs.Dir`]: fs.html#fs_class_fs_dir
[`fs.readFileSync`]: fs.html#fs_fs_readfilesync_path_options
[`fs.readdir`]: fs.html#fs_fs_readdir_path_options_callback
[`fs.symlink()`]: fs.html#fs_fs_symlink_target_path_type_callback
[`fs.symlinkSync()`]: fs.html#fs_fs_symlinksync_target_path_type
[`fs.unlink`]: fs.html#fs_fs_unlink_path_callback
[`fs`]: fs.html
[`hash.digest()`]: crypto.html#crypto_hash_digest_encoding
[`hash.update()`]: crypto.html#crypto_hash_update_data_inputencoding
[`http`]: http.html
[`https`]: https.html
[`libuv Error handling`]: http://docs.libuv.org/en/v1.x/errors.html
[`net`]: net.html
[`new URL(input)`]: url.html#url_constructor_new_url_input_base
[`new URLSearchParams(iterable)`]: url.html#url_constructor_new_urlsearchparams_iterable
[`process.send()`]: process.html#process_process_send_message_sendhandle_options_callback
[`process.setUncaughtExceptionCaptureCallback()`]: process.html#process_process_setuncaughtexceptioncapturecallback_fn
[`readable._read()`]: stream.html#stream_readable_read_size_1
[`require('crypto').setEngine()`]: crypto.html#crypto_crypto_setengine_engine_flags
[`require()`]: modules.html#modules_require_id
[`server.close()`]: net.html#net_server_close_callback
[`server.listen()`]: net.html#net_server_listen
[`sign.sign()`]: crypto.html#crypto_sign_sign_privatekey_outputencoding
[`stream.pipe()`]: stream.html#stream_readable_pipe_destination_options
[`stream.push()`]: stream.html#stream_readable_push_chunk_encoding
[`stream.unshift()`]: stream.html#stream_readable_unshift_chunk_encoding
[`stream.write()`]: stream.html#stream_writable_write_chunk_encoding_callback
[`subprocess.kill()`]: child_process.html#child_process_subprocess_kill_signal
[`subprocess.send()`]: child_process.html#child_process_subprocess_send_message_sendhandle_options_callback
[`util.getSystemErrorName(error.errno)`]: util.html#util_util_getsystemerrorname_err
[`zlib`]: zlib.html
[ES Module]: esm.html
[ICU]: intl.html#intl_internationalization_support
[Node.js Error Codes]: #nodejs-error-codes
[V8's stack trace API]: https://github.com/v8/v8/wiki/Stack-Trace-API
[WHATWG Supported Encodings]: util.html#util_whatwg_supported_encodings
[WHATWG URL API]: url.html#url_the_whatwg_url_api
[crypto digest algorithm]: crypto.html#crypto_crypto_gethashes
[domains]: domain.html
[event emitter-based]: events.html#events_class_eventemitter
[file descriptors]: https://en.wikipedia.org/wiki/File_descriptor
[policy]: policy.html
[stream-based]: stream.html
[syscall]: http://man7.org/linux/man-pages/man2/syscalls.2.html
[Subresource Integrity specification]: https://www.w3.org/TR/SRI/#the-integrity-attribute
[try-catch]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/try...catch
[vm]: vm.html
|