microsoft / microsoft/TypeScript

Namespaces: use before declaration is not reported

Offen
#61,891 4 Kommentare 3 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bug Domain: check: Control Flow Help Wanted
Vorherrschende Sprache
Go
Sterne
111k
Forks
14.3k
Ø Merge
2 T. 4 Std.
Gemergte PRs (30 T.)
132

Beschreibung

### 🔎 Search Terms

Namespace, use before declaration, initialized variable

### 🕗 Version & Regression Information

- This is the behavior in every version I tried.

### ⏯ Playground Link

https://www.typescriptlang.org/play/?target=99&jsx=0&module=1&ts=5.9.0-dev.20250618#code/KYDwDg9gTgLgBAOwIYFtgGcxIMbDgQQG8AoOOUSWRVDLXAgRjhLLIunmwgXXgDMEcALxwAFAEphAPjgAiXlACWCAOazScAL7EN7KsjSYcefACYWrPZ2684SKFCQBPYXADa+AMwA6AG5IAGwBXYABdDW1dcA5qQzoTTws2aKouHnh-YLwRfAZvAQkI4k0gA

### 💻 Code

```ts
export namespace A{
export namespace A1 {
export const fn = () => "string"
}

export namespace A2{
// should report use before initialization here
export const array = [A3.value]
}

export namespace A3{
export const value = A1.fn()
}
}
```

### 🙁 Actual behavior

Hi, using typescript V5+, the code provided did not reports any errors, and doesn't work in runtime due to use before initialization.

### 🙂 Expected behavior

It is expected that TS2448 and TS2454 will be reported.(use before declaration)
These are reported if the namespace keyword is omitted in the code example and it should be the same when namespaces are used.
It seems files with namespaces are always transpiled with the same format using any TS configuration. (everything becomes iife)

### Additional information about the issue

Optimistically additional support for namespace will be added, such as not transforming the entire file to iife when namespaces are used- which happen on any configuration.

And maybe even an option to make a code like I've sent work, by isolating these namespaces properly, and resort their order by their variable dependencies between themselves, and report when cycling variable dependency between namespaces exists.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.