microsoft / microsoft/TypeScript

"await x as any" - Node PartiallyEmittedExpression did not pass test 'isLeftHandSideExpression' assert triggered

Aperta
#62,072 1 commento 1 reazione 1 assegnatario Vedi su GitHub

Nessuno ha ancora preso questa issue.

Bug Domain: API: Transforms Help Wanted
Lingua principale
Go
Stelle
111k
Fork
14.3k
Merge medio
2g 4h
PR unite (30g)
132

Descrizione

### 🔎 Search Terms

"PartiallyEmittedExpression", "isLeftHandSideExpression", "NODE_ENV" "NODE_ENV=development"

### 🕗 Version & Regression Information

This is the behavior in every version I tried (4.0, 5.0, and 5.8.3), and I reviewed the FAQ to see if anything related was in there

### ⏯ Playground Link

_No response_

### 💻 Code

```ts
async function test() {
const test = (await null as any)!;
};
```

Executing this code in the Playground will be fine, but the bug can be triggered by running tsc with env var NODE_ENV=development turned on.

### 🙁 Actual behavior

Executing this code in the Playground will be fine, but running this with tsc on the command line with env flag NODE_ENV=development will fail with the following error:

```
Error: Debug Failure. False expression: Unexpected node.
Verbose Debug Information: Node PartiallyEmittedExpression did not pass test 'isLeftHandSideExpression'.
```

We did not realize NODE_ENV=development would affect TypeScript, and start throwing errors on code that normally compiles perfectly fine.

### 🙂 Expected behavior

Either NODE_ENV=development should not affect TypeScript at all, or at least TypeScript shouldn't crash when hitting some debug path? If this behavior is expected then putting an item in the FAQ about ensuring NODE_ENV is not set to development might be sensible.

### Additional information about the issue

_No response_

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.