Repository navigation
regression: Private fields appear in type literal in declarations (5.9) #62153
Description
🔎 Search Terms
private declaration
🕗 Version & Regression Information
- This changed between versions 5.8 and 5.9
⏯ Playground Link
💻 Code
export const ClassExpression = class {
#context = 0
};🙁 Actual behavior
Declaration file contains invalid syntax
export declare const ClassExpression: {
new (): {
#context: number;
};
};🙂 Expected behavior
5.8 output is also incorrect but at least syntactically valid
export declare const ClassExpression: {
new (): {
"__#1@#context": number;
};
};Additional information about the issue
No response
Activity
[-]regression: Private fields appear in type literal in declarations[/-][+]regression: Private fields appear in type literal in declarations (5.9)[/+]jakebailey commentedon Jul 31, 2025
Bisects to #61492, somehow. Gabriela Araujo Britto (@gabritto)
weswigham commentedon Jul 31, 2025
I imagine expandable hover fixed printback of private props to be actual private props and not internal symbol names, so they could be displayed in the expansion. Really, this should be an error during declaration emit, like the
privatecase is.