mirror of
https://github.com/denoland/deno.git
synced 2025-03-03 09:31:22 -05:00
docs: end sentences with a period in docs (#7730)
This commit is contained in:
parent
1437838ea1
commit
8ceb165e5d
4 changed files with 12 additions and 12 deletions
|
@ -141,5 +141,5 @@ Deno process.
|
|||
Devtools support is still immature. There is some functionality that is known to
|
||||
be missing or buggy:
|
||||
|
||||
- autocomplete in Devtools' console causes the Deno process to exit
|
||||
- profiling and memory dumps might not work correctly
|
||||
- autocomplete in Devtools' console causes the Deno process to exit.
|
||||
- profiling and memory dumps might not work correctly.
|
||||
|
|
|
@ -36,7 +36,7 @@ have been historically written with bash or python.
|
|||
## Goals
|
||||
|
||||
- Only ship a single executable (`deno`).
|
||||
- Provide Secure Defaults
|
||||
- Provide Secure Defaults.
|
||||
- Unless specifically allowed, scripts can't access files, the environment, or
|
||||
the network.
|
||||
- Browser compatible: The subset of Deno programs which are written completely
|
||||
|
@ -45,12 +45,12 @@ have been historically written with bash or python.
|
|||
- Provide built-in tooling like unit testing, code formatting, and linting to
|
||||
improve developer experience.
|
||||
- Does not leak V8 concepts into user land.
|
||||
- Be able to serve HTTP efficiently
|
||||
- Be able to serve HTTP efficiently.
|
||||
|
||||
## Comparison to Node.js
|
||||
|
||||
- Deno does not use `npm`
|
||||
- It uses modules referenced as URLs or file paths
|
||||
- Deno does not use `npm`.
|
||||
- It uses modules referenced as URLs or file paths.
|
||||
- Deno does not use `package.json` in its module resolution algorithm.
|
||||
- All async actions in Deno return a promise. Thus Deno provides different APIs
|
||||
than Node.
|
||||
|
|
|
@ -9,10 +9,10 @@ You can use import maps with the `--importmap=<FILE>` CLI flag.
|
|||
|
||||
Current limitations:
|
||||
|
||||
- single import map
|
||||
- no fallback URLs
|
||||
- Deno does not support `std:` namespace
|
||||
- supports only `file:`, `http:` and `https:` schemes
|
||||
- single import map.
|
||||
- no fallback URLs.
|
||||
- Deno does not support `std:` namespace.
|
||||
- supports only `file:`, `http:` and `https:` schemes.
|
||||
|
||||
Example:
|
||||
|
||||
|
|
|
@ -17,14 +17,14 @@ deno cache --reload my_module.ts
|
|||
Sometimes we want to upgrade only some modules. You can control it by passing an
|
||||
argument to a `--reload` flag.
|
||||
|
||||
To reload all \$STD_VERSION standard modules
|
||||
To reload all \$STD_VERSION standard modules:
|
||||
|
||||
```ts
|
||||
deno cache --reload=https://deno.land/std@$STD_VERSION my_module.ts
|
||||
```
|
||||
|
||||
To reload specific modules (in this example - colors and file system copy) use a
|
||||
comma to separate URLs
|
||||
comma to separate URLs.
|
||||
|
||||
```ts
|
||||
deno cache --reload=https://deno.land/std@$STD_VERSION/fs/copy.ts,https://deno.land/std@$STD_VERSION/fmt/colors.ts my_module.ts
|
||||
|
|
Loading…
Add table
Reference in a new issue