-
Notifications
You must be signed in to change notification settings - Fork 12.8k
transpileModule fails when declarationMap is specified #59641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Technically a dupe of #31991 but it's been a while |
I honestly searched for an existing bug but did not find it :( It's strange that this is newly impacting us. We did not have an issue before 5.5 RTM. |
I only found that issue last night because I sorted all issues by least recently modified to find closable/interesting issues π (But searching "transpileModule declarationMap" also worked) |
I'd suspect it was #58261 |
Yeah probably. I also though so, that's why I searched for newest issues instead of going back to 2019. I was convinced it's a recent regression. |
My guess would be that it was actually "fixed" a while ago, then re-broken again. |
π Search Terms
transpileModule declarationMap
π Version & Regression Information
β― Playground Link
No response
π» Code
No response
π Actual behavior
When calling transpileModule with options that specify both
declaration
anddeclarationMap
,transpileModule
will force to falsedeclaration
but will leavedeclarationMap
as is resulting in the error:error TS5069: Option 'declarationMap' cannot be specified without specifying option 'declaration' or option 'composite'.
π Expected behavior
transpileModule
should set bothdeclaration
anddeclarationMap
to false (or neither)Additional information about the issue
No response
The text was updated successfully, but these errors were encountered: