Skip to content
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

[TS] Generated type definitions incorrect #8048

Closed
levino opened this issue May 3, 2022 · 4 comments
Closed

[TS] Generated type definitions incorrect #8048

levino opened this issue May 3, 2022 · 4 comments

Comments

@levino
Copy link

levino commented May 3, 2022

🐛 bug report

Under certain conditions incorrect / broken type definitions are being generated.

🎛 Configuration (.babelrc, package.json, cli command)

See demo repo.

🤔 Expected Behavior

The type definitions should be correct and reflect all typings.

😯 Current Behavior

The type definitions use some incorrect import statements which render the output type definitions useless for usage in third party projects.

💁 Possible Solution

I do not know. But if I do not export the type here the problem goes away (the types are correctly inlined in the output file).

🔦 Context

I wanted to bundle a typescript library with multiple files into one output JS file and one output types.d.ts file.

💻 Code Sample

https://github.com/Levino/parcel-ts-bug/blob/bee242fed0acedcbb7e313bbf974f22a7de8d818/dist/index.d.ts#L2

🌍 Your Environment

Please see the demo repo.

@github-actions
Copy link

github-actions bot commented Nov 1, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.

@github-actions github-actions bot added the Stale Inactive issues label Nov 1, 2022
@sseidel16
Copy link

This is a serious issue that still exists.

@github-actions github-actions bot removed the Stale Inactive issues label Sep 26, 2024
@levino
Copy link
Author

levino commented Sep 26, 2024

Yeah. Just use something else. This bundler is not worth the trouble.

@sseidel16
Copy link

@levino unfortunately I have to agree with you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants