You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting unbound type-parameters in a declaration file generated for an index.ts entry which exports types from two modules. The exports have overlapping parameter names but don't reference each other or conflict in any way. Rather than preserving the original type-parameter names, new (undeclared) names are used in the body of the declaration, which results in the following error:
Cannot find name 'T$0'.
The unbound parameter names are of the form <letter><dollar><number>, e.g. T$0, R$0. These names aren't used in the code, and aren't generated for the standalone modules, only for the merged index declaration. I can't reproduce this with tsc, but then it doesn't merge the declarations.
Hey there. Thanks for the repro, and sorry for the late follow-up. This problem was caused by the deconflicting layer of the declaration bundler that didn't handle CallSignatureDeclarations. I've added support for nodes of that kind in this commit and it will be published to npm as soon as possible.
keywords: alias, dollar, dollars, interface, mangle, mangled, mangling, name, naming, parameter, rename, undeclared
System
Description
I'm getting unbound type-parameters in a declaration file generated for an
index.ts
entry which exports types from two modules. The exports have overlapping parameter names but don't reference each other or conflict in any way. Rather than preserving the original type-parameter names, new (undeclared) names are used in the body of the declaration, which results in the following error:The unbound parameter names are of the form
<letter><dollar><number>
, e.g.T$0
,R$0
. These names aren't used in the code, and aren't generated for the standalone modules, only for the merged index declaration. I can't reproduce this withtsc
, but then it doesn't merge the declarations.Reproduction
Expected Behavior
Actual Behavior
See Also
The text was updated successfully, but these errors were encountered: