GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — doc: improve wording in vm.md · nodejs/node@3d752cd

File tree

Expand file treeCollapse file tree
Open diff view settings
Filter options
  • doc/api
    • vm.md
Expand file treeCollapse file tree
Open diff view settings
Collapse file

‎doc/api/vm.md‎

Copy file name to clipboardExpand all lines: doc/api/vm.md
+2-3Lines changed: 2 additions & 3 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -312,9 +312,8 @@ specification.
312312

313313
Unlike `vm.Script` however, every `vm.Module` object is bound to a context from
314314
its creation. Operations on `vm.Module` objects are intrinsically asynchronous,
315-
in contrast with the synchronous nature of `vm.Script` objects. With the help
316-
of async functions, however, manipulating `vm.Module` objects is fairly
317-
straightforward.
315+
in contrast with the synchronous nature of `vm.Script` objects. The use of
316+
'async' functions can help with manipulating `vm.Module` objects.
318317

319318
Using a `vm.Module` object requires three distinct steps: creation/parsing,
320319
linking, and evaluation. These three steps are illustrated in the following

0 commit comments

Comments
0 (0)
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.