await an expression with surrogate characters raises a SyntaxError

[Mesteery]

Version

16.8.0

Platform

No response

Subsystem

repl

What steps will reproduce the bug?

$ node
Welcome to Node.js v16.8.0.
Type ".help" for more information.
> await '😀😀😀' // or
> await '😀😀😀'; // or
> await '😀😀😀';;

How often does it reproduce? Is there a required condition?

All the time, as long as there is a top level await with one or more surrogate chars with a semicolon, or at least 3 surrogate chars.

What is the expected behavior?

> await '😀😀😀'
'😀😀😀'

What do you see instead?

> await '😀😀😀'
 }))()
 ^

Uncaught SyntaxError: Unexpected token '}'

> await '😀😀😀';
(async () => { return (await '😀😀😀';
                                     ^

Uncaught SyntaxError: Unexpected token ';'

> await '😀😀😀';;
undefined

Additional information

This is obviously reproducible with a more complex expression (for example await new buffer.Blob(['aaa', Buffer.from('èèee😁😁😁aaa')]).text().

[targos]

@nodejs/repl

[Mesteery]

By the way there is another unrelated bug: await <any>;; != <any>;;. I don't know if this is intentional. Should I do another issue?

> await 1;;
undefined
> 1;;
1

[Ayase-252]

@Mesteery I think it is a seperate issue. it would be worth to open a new issue. 🤔

Output from chrome dev tool

[devsnek]

the infinite stream of bugs for fake tla is even better than I thought it would be