foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-26 16:09:27 -05:00
Code Issues Packages 1 Wiki Activity

Fix some deno.land URLs in the manual (#3205)

Browse source
This commit is contained in:
Nayeem Rahman 2019-10-26 15:40:13 +01:00 committed by Ry Dahl
parent 1a86264232
commit 585993c8d5
1 changed files with 8 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
std/manual.md
View file

@ -150,7 +150,7 @@ executable bit on Mac and Linux.
Once it's installed and in your `$PATH`, try it: Once it's installed and in your `$PATH`, try it:
```shell ```shell
deno https://deno.land/welcome.ts deno https://deno.land/std/examples/welcome.ts
``` ```
### Build from source ### Build from source
@ -419,7 +419,7 @@ a comma to separate URLs
Deno also provides permissions whitelist. Deno also provides permissions whitelist.
This is an example to restrict File system access by whitelist. This is an example to restrict file system access by whitelist.
```shell ```shell
$ deno --allow-read=/usr https://deno.land/std/examples/cat.ts /etc/passwd $ deno --allow-read=/usr https://deno.land/std/examples/cat.ts /etc/passwd
@ -589,18 +589,20 @@ everywhere in a large project?** The solution is to import and re-export your
external libraries in a central `deps.ts` file (which serves the same purpose as external libraries in a central `deps.ts` file (which serves the same purpose as
Node's `package.json` file). For example, let's say you were using the above Node's `package.json` file). For example, let's say you were using the above
testing library across a large project. Rather than importing testing library across a large project. Rather than importing
`"https://deno.land/std/testing/mod.ts"` everywhere, you could create a `"https://deno.land/std/testing/mod.ts"` and
`"https://deno.land/std/testing/asserts.ts"` everywhere, you could create a
`deps.ts` file that exports the third-party code: `deps.ts` file that exports the third-party code:
```ts ```ts
export { test, assertEquals } from "https://deno.land/std/testing/mod.ts"; export { runTests, test } from "https://deno.land/std/testing/mod.ts";
export { assertEquals } from "https://deno.land/std/testing/asserts.ts";
``` ```
And throughout the same project, you can import from the `deps.ts` and avoid And throughout the same project, you can import from the `deps.ts` and avoid
having many references to the same URL: having many references to the same URL:
```ts ```ts
import { test, assertEquals } from "./deps.ts"; import { assertEquals, runTests, test } from "./deps.ts";
``` ```
This design circumvents a plethora of complexity spawned by package management This design circumvents a plethora of complexity spawned by package management
@ -679,7 +681,7 @@ To run the REPL:
To execute a sandboxed script: To execute a sandboxed script:
deno https://deno.land/welcome.ts deno https://deno.land/std/examples/welcome.ts
To evaluate code from the command line: To evaluate code from the command line: