{"push_id":1310953691,"size":3,"distinct_size":1,"ref":"refs/heads/webpack","head":"d49f4aef12f514ab4116b694c7fdd93b73e6fe79","before":"750fd86fd8272af60db0cc4e4267c53f8579c3f8","commits":[{"sha":"98e2d30a9991ab2e2cc4b8ee650d29002b8964ef","author":{"name":"hristoterezov","email":"4669287f2a404b0c05c00a721f4a375b0d716b9f@jitsi.org"},"message":"fix(RTC): Use import instead of require for JitsiTrackError","distinct":false,"url":"https://api.github.com/repos/jitsi/lib-jitsi-meet/commits/98e2d30a9991ab2e2cc4b8ee650d29002b8964ef"},{"sha":"4d33a029bfaf5c47cb6035a07213f0842475efba","author":{"name":"Любомир Маринов","email":"af078e0d30d8b2e5793add4645afd5456e00834d@jitsi.org"},"message":"Merge pull request #257 from jitsi/fix_jitsi_track_error_import\n\nfix(RTC): Use import instead of require for JitsiTrackError","distinct":false,"url":"https://api.github.com/repos/jitsi/lib-jitsi-meet/commits/4d33a029bfaf5c47cb6035a07213f0842475efba"},{"sha":"d49f4aef12f514ab4116b694c7fdd93b73e6fe79","author":{"name":"Lyubomir Marinov","email":"af078e0d30d8b2e5793add4645afd5456e00834d@jitsi.org"},"message":"Switch from Browserify to Webpack\n\n1. The minimized versions of the library lib-jitsi-meet i.e. the file\n   lib-jitsi-meet.js with the default configurations of Browserify and\n   Webpack are, respectively, 614KB and 424KB. That's a reduction in\n   file size of approximately 30%. While such a reduction may be\n   achieved with Browserify, such a configuration would be non-default\n   i.e. it would be more complex.\n\n2. The build process of the library lib-jitsi-meet with Browserify is\n   split into three distinct steps by package.json: transpile, version,\n   and minimize. The transpile step produces a .js file and a source map\n   which get consumed by the minimize step (as input files). A possible\n   problem appears during the version step which modifies the .js file\n   without modifying the respective source map. Thus, there is a risk\n   that the source map of the minimized version of the library\n   lib-jitsi-meet is broken. The Webpack approach carries out the\n   version step in a way that precludes the possible breaking of the\n   source map.\n\n3. The introduction of ES2015 forced us to split the Babel-related parts\n   of the build process out of package.json into start_browserify.js. As\n   may be seen by comparing start_browserify.js and webpack.config.js,\n   there are similarities. The advantage of Webpack is that the other\n   parts of the build process are inside webpack.config.js as well. In\n   other words, there is no split in the build process and there is less\n   complexity.","distinct":true,"url":"https://api.github.com/repos/jitsi/lib-jitsi-meet/commits/d49f4aef12f514ab4116b694c7fdd93b73e6fe79"}]}
{"actor":{"display_login":"lyubomir"}}