Open thasmo opened 6 years ago
Not sure where you got those numbers from:
Obviously v3 did increase file size, but the result is much more features, a cleaner code base, better API, etc, etc.
I do want to look at being able to include/exclude parts of the player as that would definitely help with filesize. Currently it's all dependent on each other.
Any help with this is appreciated...
Just to be clear, I'm refering to the minified file sizes, which are also the sizes browser need to parse and execute, not the minified and gzipped sizes, which are only relevant for transfer time.
I'd love to see this too. I'm using Plyr exclusively for audio, so a lot of the code isn't needed in this case. So I'm not upgrading from v2 yet.
plyr
(v2) caught my eye, because it had a reasonable size (~40 KiB minified) while still supporting lots of features. I noticed thatv3
minified has ~90 KiB now. Although this is still a lot less than e.g.video.js
I'd like to point out that (for me) one feature ofplyr
is/was it's small size.Have there been thoughts about making features modular so developers can add functionality on demand while keeping the footprint small?
Thanks for making
plyr
!