microsoft / microsoft/TypeScript

Namespaces: use before declaration is not reported

Ouverte
#61,891 4 commentaires 3 réactions 1 personne assignée Voir sur GitHub

Personne n'a encore pris cette issue.

Bug Domain: check: Control Flow Help Wanted
Langage dominant
Go
Étoiles
111k
Forks
14.3k
Merge moyen
2 j 4 h
PR mergées (30 j)
132

Description

### 🔎 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.

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.