In node.js REPL, after evaluating "global", accessing anything from global scope causes TS2669

[panta82]

Expected Behavior

You can do something like:

> global // show global object
> Number // prints "[Function: Number]"

Actual Behavior

Steps to reproduce the problem

1. Install @types/node
2. Start ts-node in REPL mode
3. Type "global"
4. Type "Number"

Minimal reproduction

https://github.com/panta82/ts-node-minimal-reproduction

Specifications

• ts-node v8.10.2
• node v14.4.0
• compiler v3.9.5
• Operating system and version: Linux 5.4.0-37-generic 18.04.1-Ubuntu

[cspotcode]

The REPL has to concatenate each line of input into a single TypeScript file. My guess is the concatenation in this case is going wrong, so it's concatenating into something similar to `global { Number }`.

…

On Sun, Jun 21, 2020, 4:10 AM Ivan Pantic ***@***.***> wrote: Expected Behavior You can do something like: > global // show global object > Number // prints "[Function: Number]" Actual Behavior [image: image] <https://user-images.githubusercontent.com/4291324/85219587-89237700-b3a5-11ea-911a-b0117abe55f5.png> Steps to reproduce the problem 1. Install @types/node 2. Start ts-node in REPL mode 3. Type "global" 4. Type "Number" Minimal reproduction https://github.com/panta82/ts-node-minimal-reproduction Specifications - ts-node v8.10.2 - node v14.4.0 - compiler v3.9.5 - Operating system and version: Linux 5.4.0-37-generic 18.04.1-Ubuntu — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1067>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC35OD42XIEWYSZ3VGWDDTRXW56ZANCNFSM4ODX6KEQ> .

[cspotcode]

Marked as "help wanted" to indicate that we will wait for a pull request fixing this bug. It's minor and seems like a straightforward contribution.

[ejose19]

FWIW, this issue no longer reproduces on latest versions (10.2.1+)

[cspotcode]

Good catch, looks like this was fixed by #1480. That was released in 10.3.0, and I can reproduce this issue on 10.2.1 but not on 10.3.0.