| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 522fbbc commit 8e3a0d7
13 files changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -285,7 +285,7 @@ console.error(err.message); | |||
| 285 | 285 | The `error.stack` property is a string describing the point in the code at which | |
| 286 | 286 | the `Error` was instantiated. | |
| 287 | 287 | ||
| 288 | - ```txt | ||
| 288 | + ```console | ||
| 289 | 289 | Error: Things keep happening! | |
| 290 | 290 | at /home/gbusey/file.js:525:2 | |
| 291 | 291 | at Frobnicator.refrobulate (/home/gbusey/business-logic.js:424:21) | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -3544,7 +3544,7 @@ is recommended. | |||
| 3544 | 3544 | ||
| 3545 | 3545 | For example, given the following directory structure: | |
| 3546 | 3546 | ||
| 3547 | - ```fundamental | ||
| 3547 | + ```text | ||
| 3548 | 3548 | - txtDir | |
| 3549 | 3549 | -- file.txt | |
| 3550 | 3550 | - app.js | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -2049,7 +2049,7 @@ added: v0.1.90 | |||
| 2049 | 2049 | Request URL string. This contains only the URL that is | |
| 2050 | 2050 | present in the actual HTTP request. If the request is: | |
| 2051 | 2051 | ||
| 2052 | - ```txt | ||
| 2052 | + ```http | ||
| 2053 | 2053 | GET /status?name=ryan HTTP/1.1\r\n | |
| 2054 | 2054 | Accept: text/plain\r\n | |
| 2055 | 2055 | \r\n | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -3022,7 +3022,7 @@ added: v8.4.0 | |||
| 3022 | 3022 | Request URL string. This contains only the URL that is | |
| 3023 | 3023 | present in the actual HTTP request. If the request is: | |
| 3024 | 3024 | ||
| 3025 | - ```txt | ||
| 3025 | + ```http | ||
| 3026 | 3026 | GET /status?name=ryan HTTP/1.1\r\n | |
| 3027 | 3027 | Accept: text/plain\r\n | |
| 3028 | 3028 | \r\n | |
@@ -3038,7 +3038,7 @@ Then `request.url` will be: | |||
| 3038 | 3038 | To parse the url into its parts `require('url').parse(request.url)` | |
| 3039 | 3039 | can be used: | |
| 3040 | 3040 | ||
| 3041 | - ```txt | ||
| 3041 | + ```console | ||
| 3042 | 3042 | $ node | |
| 3043 | 3043 | > require('url').parse('/status?name=ryan') | |
| 3044 | 3044 | Url { | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -149,7 +149,7 @@ the `require.resolve()` function. | |||
| 149 | 149 | Putting together all of the above, here is the high-level algorithm | |
| 150 | 150 | in pseudocode of what `require()` does: | |
| 151 | 151 | ||
| 152 | - ```txt | ||
| 152 | + ```text | ||
| 153 | 153 | require(X) from module at path Y | |
| 154 | 154 | 1. If X is a core module, | |
| 155 | 155 | a. return the core module | |
@@ -409,7 +409,7 @@ example, then `require('./some-library')` would attempt to load: | |||
| 409 | 409 | If these attempts fail, then Node.js will report the entire module as missing | |
| 410 | 410 | with the default error: | |
| 411 | 411 | ||
| 412 | - ```txt | ||
| 412 | + ```console | ||
| 413 | 413 | Error: Cannot find module 'some-library' | |
| 414 | 414 | ``` | |
| 415 | 415 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -503,7 +503,7 @@ containing `libuv` handle information and an OS platform information section | |||
| 503 | 503 | showing CPU and memory usage and system limits. An example report can be | |
| 504 | 504 | triggered using the Node.js REPL: | |
| 505 | 505 | ||
| 506 | - ```raw | ||
| 506 | + ```console | ||
| 507 | 507 | $ node | |
| 508 | 508 | > process.report.writeReport(); | |
| 509 | 509 | Writing Node.js report to file: report.20181126.091102.8480.0.001.json | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -272,7 +272,7 @@ Reused, TLSv1.2, Cipher is ECDHE-RSA-AES128-GCM-SHA256 | |||
| 272 | 272 | Node.js is built with a default suite of enabled and disabled TLS ciphers. | |
| 273 | 273 | Currently, the default cipher suite is: | |
| 274 | 274 | ||
| 275 | - ```txt | ||
| 275 | + ```text | ||
| 276 | 276 | TLS_AES_256_GCM_SHA384: | |
| 277 | 277 | TLS_CHACHA20_POLY1305_SHA256: | |
| 278 | 278 | TLS_AES_128_GCM_SHA256: | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -36,7 +36,7 @@ The available categories are: | |||
| 36 | 36 | ||
| 37 | 37 | By default the `node`, `node.async_hooks`, and `v8` categories are enabled. | |
| 38 | 38 | ||
| 39 | - ```txt | ||
| 39 | + ```bash | ||
| 40 | 40 | node --trace-event-categories v8,node,node.async_hooks server.js | |
| 41 | 41 | ``` | |
| 42 | 42 | ||
@@ -45,10 +45,10 @@ flag to enable trace events. This requirement has been removed. However, the | |||
| 45 | 45 | `--trace-events-enabled` flag *may* still be used and will enable the | |
| 46 | 46 | `node`, `node.async_hooks`, and `v8` trace event categories by default. | |
| 47 | 47 | ||
| 48 | - ```txt | ||
| 48 | + ```bash | ||
| 49 | 49 | node --trace-events-enabled | |
| 50 | 50 | ||
| 51 | - // is equivalent to | ||
| 51 | + # is equivalent to | ||
| 52 | 52 | ||
| 53 | 53 | node --trace-event-categories v8,node,node.async_hooks | |
| 54 | 54 | ``` | |
@@ -74,7 +74,7 @@ The logging file is by default called `node_trace.${rotation}.log`, where | |||
| 74 | 74 | be specified with `--trace-event-file-pattern` that accepts a template | |
| 75 | 75 | string that supports `${rotation}` and `${pid}`: | |
| 76 | 76 | ||
| 77 | - ```txt | ||
| 77 | + ```bash | ||
| 78 | 78 | node --trace-event-categories v8 --trace-event-file-pattern '${pid}-${rotation}.log' server.js | |
| 79 | 79 | ``` | |
| 80 | 80 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -29,7 +29,7 @@ properties of a WHATWG `URL` object. | |||
| 29 | 29 | WHATWG URL's `origin` property includes `protocol` and `host`, but not | |
| 30 | 30 | `username` or `password`. | |
| 31 | 31 | ||
| 32 | - ```txt | ||
| 32 | + ```text | ||
| 33 | 33 | ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ | |
| 34 | 34 | │ href │ | |
| 35 | 35 | ├──────────┬──┬─────────────────────┬────────────────────────┬───────────────────────────┬───────┤ | |
@@ -1288,7 +1288,7 @@ located within the structure of the URL. | |||
| 1288 | 1288 | Within the Legacy API, spaces (`' '`) and the following characters will be | |
| 1289 | 1289 | automatically escaped in the properties of URL objects: | |
| 1290 | 1290 | ||
| 1291 | - ```txt | ||
| 1291 | + ```text | ||
| 1292 | 1292 | < > " ` \r \n \t { } | \ ^ ' | |
| 1293 | 1293 | ``` | |
| 1294 | 1294 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -42,7 +42,7 @@ callbackFunction((err, ret) => { | |||
| 42 | 42 | ||
| 43 | 43 | Will print: | |
| 44 | 44 | ||
| 45 | - ```txt | ||
| 45 | + ```text | ||
| 46 | 46 | hello world | |
| 47 | 47 | ``` | |
| 48 | 48 | ||
@@ -93,7 +93,7 @@ debuglog('hello from foo [%d]', 123); | |||
| 93 | 93 | If this program is run with `NODE_DEBUG=foo` in the environment, then | |
| 94 | 94 | it will output something like: | |
| 95 | 95 | ||
| 96 | - ```txt | ||
| 96 | + ```console | ||
| 97 | 97 | FOO 3245: hello from foo [123] | |
| 98 | 98 | ``` | |
| 99 | 99 | ||
@@ -112,7 +112,7 @@ debuglog('hi there, it\'s foo-bar [%d]', 2333); | |||
| 112 | 112 | if it is run with `NODE_DEBUG=foo*` in the environment, then it will output | |
| 113 | 113 | something like: | |
| 114 | 114 | ||
| 115 | - ```txt | ||
| 115 | + ```console | ||
| 116 | 116 | FOO-BAR 3257: hi there, it's foo-bar [2333] | |
| 117 | 117 | ``` | |
| 118 | 118 | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments