-
Notifications
You must be signed in to change notification settings - Fork 29
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
out of memory if too many conditional exports #423
Comments
Do you have a reproduction link? did'nt see bunchee is setup in that repo |
im still working on this |
but you can overwrite the package.json and see it |
Possible you bundled sth re not in the dependencies or peer dependencies, it happened before when some users were trying to bundle webpack but actually webpack should be external |
Thanks I can repro it now, will investigate which part is having mem leak 👁️🗨️ One possible is probably due to rollup production optimization that causes a lot of memory, or it's using too much mem in ts generation plugin |
Looks like if there's no types generation they memory allocation will be fine without specifying extra memory, sth wrong with the ts generation. |
This is still happening on our case especially when increasing the exports, sadly I'm considering to switch to other bundler |
I'm rewriting the exports parser and in the shorter future we gonna generate less type files for your case which could help a bit on the memory. I can't commit a time that can fix this soon since the resource from me on this is pretty limited atm. |
So the generating more types file is not the main problem. Seems ts plugin will consume too much memory anyway. I might need to move those work to a separate worker |
Tested with the repro, it's resolved with 5.0.0-beta.2 |
@himself65 [email protected] improved more about the types generation perf for multi exports! 🙏 |
The text was updated successfully, but these errors were encountered: