microsoft / microsoft/TypeScript

When using a string value as export for reference, the .d.ts file created with dot notation instead of computed property which can break

Ouverte
#61,159 0 commentaires 1 réaction 1 personne assignée Voir sur GitHub

@rbuckton y travaille déjà.

Depuis le 10/2/2025.

Bug Domain: Declaration Emit
Langage dominant
Go
Étoiles
111k
Forks
14.3k
Merge moyen
2 j 4 h
PR mergées (30 j)
132

Description

### 🔎 Search Terms

references, string exports

### 🕗 Version & Regression Information

- This changed between versions 5.6 and 5.7.3
- ~~This changed in commit or PR _______~~. It's a feature wasn't implemented fully
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about: Yes
- I was unable to test this on prior versions because: It's a new feature that isn't fully implemented (string exports)

### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/JYOwLgpgTgZghgYwgAgGIHt3IN4F8BQ+EAHgA7pRg5qbJwDOyARAH4bpPIH4D0PyAC3QB3ZABMsAV2TCowSMnkB+ZCHRhgSZGAFwqAAzaZ9ixnElh0AWgToAtqQA2EMHABGzwdAi9+wgZoCpnSO9FhqVLZQUBAIVADmwABuECCKYADkjBHI8eggIHDIbihJcI7AYnQwkFDItg7OGvn4YACepCgAKhD0VAC8ig4UYAAUGQB0PKCkFhkAlBNG6EA

### 💻 Code

A [demo repo](https://github.com/oriSomething/ts-references-bug)

```ts
// In a project with references that I forced to export a "private export". I export it as a string value which breaks .d.ts creation
interface ReferenceTo {
(value: T): T;
value: T;
}

// The `as "…"` part
export { ReferenceTo as "~ ReferenceTo" };
```

### 🙁 Actual behavior

I get the error

```
a/out/lib/y.d.ts:1:39 - error TS1110: Type expected.

1 export declare const x: import("./x").~ ReferenceTo<"x">;
~

a/out/lib/y.d.ts:1:39 - error TS1110: Type expected.

1 export declare const x: import("./x").~ ReferenceTo<"x">;
~

Found 2 errors.
```

According to @Andarist it somes to the issue as described in the [playground](https://www.typescriptlang.org/play/?#code/JYOwLgpgTgZghgYwgAgGIHt3IN4F8BQ+EAHgA7pRg5qbJwDOyARAH4bpPIH4D0PyAC3QB3ZABMsAV2TCowSMnkB+ZCHRhgSZGAFwqAAzaZ9ixnElh0AWgToAtqQA2EMHABGzwdAi9+wgZoCpnSO9FhqVLZQUBAIVADmwABuECCKYADkjBHI8eggIHDIbihJcI7AYnQwkFDItg7OGvn4YACepCgAKhD0VAC8ig4UYAAUGQB0PKCkFhkAlBNG6EA)

More in the Bluesky thread: https://bsky.app/profile/andarist.bsky.social/post/3lhrod2ysps2k

### 🙂 Expected behavior

It will export it as a computed value so it work

```ts
export declare const x: import("./x")["~ ReferenceTo"]<"x">;
```

### Additional information about the issue

More in the Bluesky thread: https://bsky.app/profile/andarist.bsky.social/post/3lhrod2ysps2k

It seems it happens with Autocomplete as well.

A [demo repo](https://github.com/oriSomething/ts-references-bug)

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.