1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: fix broken link in vm.md

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/7304
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
This commit is contained in:
Luigi Pinca 2016-06-15 08:09:16 +02:00 committed by silverwind
parent 9dfc8b9d8e
commit de9a84186e
No known key found for this signature in database
GPG Key ID: 2E62B41C93869443
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/api/vm.md
View File

@ -202,12 +202,12 @@ added: v0.3.1
* `sandbox` {Object} * `sandbox` {Object}
If given a `sandbox` object, the `vm.createContext()` method will [prepare If given a `sandbox` object, the `vm.createContext()` method will [prepare
that sandbox][#vm_what_does_it_mean_to_contextify_an_object] so that it can be that sandbox][contextified] so that it can be used in calls to
used in calls to [`vm.runInContext()`][] or [`script.runInContext()`][]. Inside [`vm.runInContext()`][] or [`script.runInContext()`][]. Inside such scripts,
such scripts, the `sandbox` object will be the global object, retaining all of the `sandbox` object will be the global object, retaining all of its existing
its existing properties but also having the built-in objects and functions any properties but also having the built-in objects and functions any standard
standard [global object][] has. Outside of scripts run by the vm module, [global object][] has. Outside of scripts run by the vm module, `sandbox` will
`sandbox` will remain unchanged. remain unchanged.
If `sandbox` is omitted (or passed explicitly as `undefined`), a new, empty If `sandbox` is omitted (or passed explicitly as `undefined`), a new, empty
[contextified][] sandbox object will be returned. [contextified][] sandbox object will be returned.
@ -384,7 +384,7 @@ console.log('localVar: ', localVar);
Because `vm.runInThisContext()` does not have access to the local scope, Because `vm.runInThisContext()` does not have access to the local scope,
`localVar` is unchanged. In contrast, [`eval()`][] *does* have access to the `localVar` is unchanged. In contrast, [`eval()`][] *does* have access to the
local scope, so the value `localVar` is changed. In this way local scope, so the value `localVar` is changed. In this way
`vm.runInThisContext()` is much like an [indirect `eval()` call][], e.g. `vm.runInThisContext()` is much like an [indirect `eval()` call][], e.g.
`(0,eval)('code')`. `(0,eval)('code')`.
## Example: Running an HTTP Server within a VM ## Example: Running an HTTP Server within a VM
@ -415,7 +415,7 @@ let code =
})`; })`;
vm.runInThisContext(code)(require); vm.runInThisContext(code)(require);
``` ```
*Note*: The `require()` in the above case shares the state with context it is *Note*: The `require()` in the above case shares the state with context it is
passed from. This may introduce risks when untrusted code is executed, e.g. passed from. This may introduce risks when untrusted code is executed, e.g.