mirror of
https://github.com/denoland/deno.git
synced 2025-03-03 09:31:22 -05:00
Fix deno imports in manual (#1867)
This commit is contained in:
parent
39ed975911
commit
1a695dd58b
1 changed files with 6 additions and 6 deletions
|
@ -337,7 +337,7 @@ Run it:
|
|||
hello
|
||||
```
|
||||
|
||||
By default when you use `deno.run()` subprocess inherits `stdin`, `stdout` and
|
||||
By default when you use `Deno.run()` subprocess inherits `stdin`, `stdout` and
|
||||
`stdout` of parent process. If you want to communicate with started subprocess
|
||||
you can use `"piped"` option.
|
||||
|
||||
|
@ -521,7 +521,7 @@ generated and cached source code is written and read to.
|
|||
|
||||
`NO_COLOR` will turn off color output if set. See https://no-color.org/. User
|
||||
code can test if `NO_COLOR` was set without having `--allow-env` by using the
|
||||
boolean constant `deno.noColor`.
|
||||
boolean constant `Deno.noColor`.
|
||||
|
||||
### V8 flags
|
||||
|
||||
|
@ -546,7 +546,7 @@ Particularly useful ones:
|
|||
| File descriptors (fd) | [Resource ids (rid)](#resources) |
|
||||
| Scheduler | Tokio |
|
||||
| Userland: libc++ / glib / boost | deno_std |
|
||||
| /proc/\$\$/stat | [deno.metrics()](#metrics) |
|
||||
| /proc/\$\$/stat | [Deno.metrics()](#metrics) |
|
||||
| man pages | deno --types |
|
||||
|
||||
#### Resources
|
||||
|
@ -557,7 +557,7 @@ would be good to be able to query the system for how many open resources there
|
|||
are.
|
||||
|
||||
```ts
|
||||
import { resources, close } from "deno";
|
||||
const { resources, close } = Deno;
|
||||
console.log(resources());
|
||||
// output like: { 0: "stdin", 1: "stdout", 2: "stderr", 3: "repl" }
|
||||
|
||||
|
@ -570,7 +570,7 @@ close(3);
|
|||
Metrics is deno's internal counters for various statics.
|
||||
|
||||
```ts
|
||||
import { metrics } from "deno";
|
||||
const { metrics } = Deno;
|
||||
console.log(metrics());
|
||||
// output like: { opsDispatched: 1, opsCompleted: 1, bytesSentControl: 40, bytesSentData: 0, bytesReceived: 176 }
|
||||
```
|
||||
|
@ -762,7 +762,7 @@ We are very concerned about making mistakes when adding new APIs. When adding an
|
|||
Op to Deno, the counterpart interfaces on other platforms should be researched.
|
||||
Please list how this functionality is done in Go, Node, Rust, and Python.
|
||||
|
||||
As an example, see how `deno.rename()` was proposed and added in
|
||||
As an example, see how `Deno.rename()` was proposed and added in
|
||||
[PR #671](https://github.com/denoland/deno/pull/671).
|
||||
|
||||
### Documenting APIs
|
||||
|
|
Loading…
Add table
Reference in a new issue