| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 72e7e1d commit 2c4f80f
8 files changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1083,7 +1083,7 @@ validating against a string property. See below for examples. | |||
| 1083 | 1083 | If specified, `message` will be the message provided by the `AssertionError` if | |
| 1084 | 1084 | the block fails to throw. | |
| 1085 | 1085 | ||
| 1086 | - Custom validation object / error instance: | ||
| 1086 | + Custom validation object/error instance: | ||
| 1087 | 1087 | ||
| 1088 | 1088 | ```js | |
| 1089 | 1089 | const err = new TypeError('Wrong value'); | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -2263,7 +2263,7 @@ mode must adhere to certain restrictions when using the cipher API: | |||
| 2263 | 2263 | bytes (`7 ≤ N ≤ 13`). | |
| 2264 | 2264 | - The length of the plaintext is limited to `2 ** (8 * (15 - N))` bytes. | |
| 2265 | 2265 | - When decrypting, the authentication tag must be set via `setAuthTag()` before | |
| 2266 | - specifying additional authenticated data and / or calling `update()`. | ||
| 2266 | + specifying additional authenticated data or calling `update()`. | ||
| 2267 | 2267 | Otherwise, decryption will fail and `final()` will throw an error in | |
| 2268 | 2268 | compliance with section 2.6 of [RFC 3610][]. | |
| 2269 | 2269 | - Using stream methods such as `write(data)`, `end(data)` or `pipe()` in CCM | |
@@ -2273,8 +2273,8 @@ mode must adhere to certain restrictions when using the cipher API: | |||
| 2273 | 2273 | option. This is not necessary if no AAD is used. | |
| 2274 | 2274 | - As CCM processes the whole message at once, `update()` can only be called | |
| 2275 | 2275 | once. | |
| 2276 | - - Even though calling `update()` is sufficient to encrypt / decrypt the message, | ||
| 2277 | - applications *must* call `final()` to compute and / or verify the | ||
| 2276 | + - Even though calling `update()` is sufficient to encrypt/decrypt the message, | ||
| 2277 | + applications *must* call `final()` to compute or verify the | ||
| 2278 | 2278 | authentication tag. | |
| 2279 | 2279 | ||
| 2280 | 2280 | ```js | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1,4 +1,4 @@ | |||
| 1 | - # UDP / Datagram Sockets | ||
| 1 | + # UDP/Datagram Sockets | ||
| 2 | 2 | ||
| 3 | 3 | <!--introduced_in=v0.10.0--> | |
| 4 | 4 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -499,8 +499,8 @@ will be present on the object: | |||
| 499 | 499 | ||
| 500 | 500 | | Type | Properties | | |
| 501 | 501 | |------|------------| | |
| 502 | - | `'A'` | `address` / `ttl` | | ||
| 503 | - | `'AAAA'` | `address` / `ttl` | | ||
| 502 | + | `'A'` | `address`/`ttl` | | ||
| 503 | + | `'AAAA'` | `address`/`ttl` | | ||
| 504 | 504 | | `'CNAME'` | `value` | | |
| 505 | 505 | | `'MX'` | Refer to [`dns.resolveMx()`][] | | |
| 506 | 506 | | `'NAPTR'` | Refer to [`dns.resolveNaptr()`][] | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -31,7 +31,7 @@ called. | |||
| 31 | 31 | ||
| 32 | 32 | All JavaScript errors are handled as exceptions that *immediately* generate | |
| 33 | 33 | and throw an error using the standard JavaScript `throw` mechanism. These | |
| 34 | - are handled using the [`try / catch` construct][try-catch] provided by the | ||
| 34 | + are handled using the [`try…catch` construct][try-catch] provided by the | ||
| 35 | 35 | JavaScript language. | |
| 36 | 36 | ||
| 37 | 37 | ```js | |
@@ -45,7 +45,7 @@ try { | |||
| 45 | 45 | ``` | |
| 46 | 46 | ||
| 47 | 47 | Any use of the JavaScript `throw` mechanism will raise an exception that | |
| 48 | - *must* be handled using `try / catch` or the Node.js process will exit | ||
| 48 | + *must* be handled using `try…catch` or the Node.js process will exit | ||
| 49 | 49 | immediately. | |
| 50 | 50 | ||
| 51 | 51 | With few exceptions, _Synchronous_ APIs (any blocking method that does not | |
@@ -90,7 +90,7 @@ Errors that occur within _Asynchronous APIs_ may be reported in multiple ways: | |||
| 90 | 90 | ||
| 91 | 91 | - A handful of typically asynchronous methods in the Node.js API may still | |
| 92 | 92 | use the `throw` mechanism to raise exceptions that must be handled using | |
| 93 | - `try / catch`. There is no comprehensive list of such methods; please | ||
| 93 | + `try…catch`. There is no comprehensive list of such methods; please | ||
| 94 | 94 | refer to the documentation of each method to determine the appropriate | |
| 95 | 95 | error handling mechanism required. | |
| 96 | 96 | ||
@@ -116,7 +116,7 @@ setImmediate(() => { | |||
| 116 | 116 | }); | |
| 117 | 117 | ``` | |
| 118 | 118 | ||
| 119 | - Errors generated in this way *cannot* be intercepted using `try / catch` as | ||
| 119 | + Errors generated in this way *cannot* be intercepted using `try…catch` as | ||
| 120 | 120 | they are thrown *after* the calling code has already exited. | |
| 121 | 121 | ||
| 122 | 122 | Developers must refer to the documentation for each method to determine | |
@@ -149,7 +149,7 @@ fs.readFile('/some/file/that/does-not-exist', errorFirstCallback); | |||
| 149 | 149 | fs.readFile('/some/file/that/does-exist', errorFirstCallback); | |
| 150 | 150 | ``` | |
| 151 | 151 | ||
| 152 | - The JavaScript `try / catch` mechanism **cannot** be used to intercept errors | ||
| 152 | + The JavaScript `try…catch` mechanism **cannot** be used to intercept errors | ||
| 153 | 153 | generated by asynchronous APIs. A common mistake for beginners is to try to | |
| 154 | 154 | use `throw` inside an error-first callback: | |
| 155 | 155 | ||
@@ -648,7 +648,7 @@ Used when a child process is being forked without specifying an IPC channel. | |||
| 648 | 648 | ### ERR_CHILD_PROCESS_STDIO_MAXBUFFER | |
| 649 | 649 | ||
| 650 | 650 | Used when the main process is trying to read data from the child process's | |
| 651 | - STDERR / STDOUT, and the data's length is longer than the `maxBuffer` option. | ||
| 651 | + STDERR/STDOUT, and the data's length is longer than the `maxBuffer` option. | ||
| 652 | 652 | ||
| 653 | 653 | <a id="ERR_CLOSED_MESSAGE_PORT"></a> | |
| 654 | 654 | ### ERR_CLOSED_MESSAGE_PORT | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -36,7 +36,7 @@ To control how ICU is used in Node.js, four `configure` options are available | |||
| 36 | 36 | during compilation. Additional details on how to compile Node.js are documented | |
| 37 | 37 | in [BUILDING.md][]. | |
| 38 | 38 | ||
| 39 | - - `--with-intl=none` / `--without-intl` | ||
| 39 | + - `--with-intl=none`/`--without-intl` | ||
| 40 | 40 | - `--with-intl=system-icu` | |
| 41 | 41 | - `--with-intl=small-icu` (default) | |
| 42 | 42 | - `--with-intl=full-icu` | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -213,7 +213,7 @@ called. Otherwise, an `ERR_SERVER_ALREADY_LISTEN` error will be thrown. | |||
| 213 | 213 | ||
| 214 | 214 | One of the most common errors raised when listening is `EADDRINUSE`. | |
| 215 | 215 | This happens when another server is already listening on the requested | |
| 216 | - `port` / `path` / `handle`. One way to handle this would be to retry | ||
| 216 | + `port`/`path`/`handle`. One way to handle this would be to retry | ||
| 217 | 217 | after a certain amount of time: | |
| 218 | 218 | ||
| 219 | 219 | ```js | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -367,7 +367,7 @@ added: v8.0.0 | |||
| 367 | 367 | ||
| 368 | 368 | Destroy the stream, and emit the passed `'error'` and a `'close'` event. | |
| 369 | 369 | After this call, the writable stream has ended and subsequent calls | |
| 370 | - to `write()` / `end()` will give an `ERR_STREAM_DESTROYED` error. | ||
| 370 | + to `write()` or `end()` will result in an `ERR_STREAM_DESTROYED` error. | ||
| 371 | 371 | Implementors should not override this method, | |
| 372 | 372 | but instead implement [`writable._destroy()`][writable-_destroy]. | |
| 373 | 373 | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments