Skip to content

doc: update example of using await in REPL #45939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
deokjinkim wants to merge 4 commits into from
Closed

doc: update example of using await in REPL #45939

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0f4446c
doc: remove limitation of using `await` in REPL
deokjinkim Dec 21, 2022
2de633c
doc: update example of using `await` in REPL
deokjinkim Dec 23, 2022
6a7ae88
add test case according to change of document in REPL
deokjinkim Jan 3, 2023
d6b4483
enhance test case
deokjinkim Jan 4, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
doc: remove limitation of using await in REPL 
Invalidating the lexical scoping of the `const` and
`let` keywords is fixed.

Fixes: #45918
  • Loading branch information
@deokjinkim
deokjinkim committed Dec 21, 2022
commit 0f4446c0bb1b701aa8036ce49a8f3a6e84e5e293
17 changes: 0 additions & 17 deletions doc/api/repl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,23 +234,6 @@ undefined
undefined
```

One known limitation of using the `await` keyword in the REPL is that
it will invalidate the lexical scoping of the `const` and `let`
keywords.

For example:

```console
> const m = await Promise.resolve(123)
undefined
> m
123
> const m = await Promise.resolve(234)
undefined
> m
234
```

[`--no-experimental-repl-await`][] shall disable top-level await in REPL.

### Reverse-i-search
Expand Down