Size optimization #962
Replies: 2 comments
|
Edit : I discovered the "sourcemap" was included in my compiled file (even if set to But still I'm around 150kb now. It's quite surprising such a size compared to the distant library (https://cdn.jsdelivr.net/npm/media-chrome@4/+esm) and its 33.4kb). |
0 replies
|
I realized my Vite dev app adds a sourceMappingUrl without my consent. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I'm discovering MediaChrome and was wondering how to reduce as much as possible its size when building a production file.
I've created a small project to test with just a Mute button feature, but on the compilation, I still see optional features included (PiP, AirPlay.....).
How can I manage to filter correctly the feature I need ?
FYI: I'm using Vite in order to treeshake.
Thank you : )
All reactions