repl: document top level await limitation with const/let · nodejs/node@620ee42 · GitHub

nodejs / node Public

• Notifications You must be signed in to change notification settings
• Fork 36.6k
• Star 120k

• Code
• Issues 632
• Pull requests 755
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit 620ee42

Browse filesBrowse the repository at this point in the historyBrowse files

jasnell

authored and

targos

committed

repl: document top level await limitation with const/let

Fixes: #17669 Signed-off-by: James M Snell <jasnell@gmail.com> PR-URL: #38449 Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>

1 parent a0c566f commit 620ee42
Copy full SHA for 620ee42

1 file changed

+17Lines changed: 17 additions & 0 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• doc/api
  • repl.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎doc/api/repl.md‎

Copy file name to clipboardExpand all lines: doc/api/repl.md

+17Lines changed: 17 additions & 0 deletions

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -233,6 +233,23 @@ undefined
233	233	undefined
234	234	```
235	235
	236	+ One known limitation of using the `await` keyword in the REPL is that
	237	+ it will invalidate the lexical scoping of the `const` and `let`
	238	+ keywords.
	239	+
	240	+ For example:
	241	+
	242	+ ```console
	243	+ > const m = await Promise.resolve(123)
	244	+ undefined
	245	+ > m
	246	+ 123
	247	+ > const m = await Promise.resolve(234)
	248	+ undefined
	249	+ > m
	250	+ 234
	251	+ ```
	252	+
236	253	### Reverse-i-search
237	254	<!-- YAML
238	255	added:

0 commit comments

Comments

0 (0)