Pixijs v7 es5 transpile and performance issues #10013
Unanswered
nicolasb-pearfiction
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
We have recently migrated from pixi.js v5 to v7 on our game framework and observed nice performance improvements in general, however our device support list is not fully compatible with es2015+. We went away with using Babel to transpile down to es5 and it fixed devices support as the game now loads. But the problem is performances have dropped significantly, worst than what they were under pixi.js 5.
We did not determine yet what exactly causes the performance drop. It could be one or two specific features that are polyfilled and not even used in pixijs's source code. Also because pixijs v5 didn't have these huge performance issues, and because it was using Buble for es5 support, it might be the case that Babel is doing something different that significantly impact performances.
It would be useful to have a full list of es2015+ features that are used in the source code so that those features can be selectively transpiled down and provided with polyfills by Babel, instead of throwing everything and the kitchen sink. Maybe this could help regarding performances. With Buble we are able to detect es2017+ features because it throws an error when it tries to parse those, but we can't detect es2015 as Buble is happy to transpile them down and doesn't throw errors so we don't have a full list at the moment.
Otherwise, is there any knowledge on what could potentially impact performances with respect to transpiling down to es5 and potential ways to fix this?
Beta Was this translation helpful? Give feedback.
All reactions