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
How do you envision this feature/change to look/work like?
When running plasmo build --bundle-buddy, it should output an instrumented zip containing instructions for developer to visualize their dependencies on https://www.bundle-buddy.com/
What is the purpose of this change/feature? Why?
We are seeing large extension projects suffering from bundle bloating - i.e, their dependency containing hidden dependencies that caused the entire bundle to bloat to about 300MB or even more. Worst yet, the parcel cache can sometimes grow to about 300GB ?!
To debug these issues, devs need to visualize and understand what is being bundled into the extension.
How do you envision this feature/change to look/work like?
When running
plasmo build --bundle-buddy
, it should output an instrumented zip containing instructions for developer to visualize their dependencies on https://www.bundle-buddy.com/What is the purpose of this change/feature? Why?
We are seeing large extension projects suffering from bundle bloating - i.e, their dependency containing hidden dependencies that caused the entire bundle to bloat to about 300MB or even more. Worst yet, the parcel cache can sometimes grow to about 300GB ?!
To debug these issues, devs need to visualize and understand what is being bundled into the extension.
(OPTIONAL) Example implementations
https://parceljs.org/features/production/#bundle-buddy
(OPTIONAL) Contact Details
No response
Verify canary release
plasmo
canary releaseCode of Conduct
The text was updated successfully, but these errors were encountered: