microsoft / microsoft/TypeScript
Declaration file emits symbol property keys without importing them
@DanielRosenwasser ci sta già lavorando.
Dal 6/2/2026.
- Lingua principale
- Go
- Stelle
- 111k
- Fork
- 14.3k
- Merge medio
- 2g 4h
- PR unite (30g)
- 132
Descrizione
### 🔎 Search Terms
missing import in d.ts, symbol key not imported, unique symbol dts emit, dataTagSymbol not found, declaration file missing import
### 🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about "Behavior That Looks Wrong (And Arguably Is) But Is Currently Working As Intended"
- This bug is reproducible in the latest stable (`5.9.2`), and still occurs in `next` (`6.0.0-dev.20250811`)
### ⏯ Playground Link
https://stackblitz.com/edit/stackblitz-starters-vflvduch?file=src%2Findex.ts
### 💻 Code
Here's the code from the Stackblitz reproduction above.
src/index.ts:
```ts
import { fn } from 'test-pkg';
export const value = fn();
```
node_modules/test-pkg/index.d.ts:
```ts
declare const lostSymbol: unique symbol;
type lostSymbol = typeof lostSymbol;
type SomeGeneric = {
[lostSymbol]: T;
};
declare function fn(): SomeGeneric;
export {
lostSymbol,
fn
};
```
### 🙁 Actual behavior
dist/index.d.ts:
```ts
export declare const value: {
[lostSymbol]: unknown; // lostSymbol is not defined here and errors on the consumer's type check
};
```
### 🙂 Expected behavior
dist/index.d.ts:
```ts
import { lostSymbol } from 'test-pkg'; // should import from pacakge
export declare const value: {
[lostSymbol]: unknown;
};
```
### Additional information about the issue
Related?: https://github.com/microsoft/TypeScript/issues/49065
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.