-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected module.runSetters wrapping #277
Comments
We seem to be experiencing a similar issue on our end when using Material-UI v5 with MeteorJS. https://forums.meteor.com/t/material-ui-v5-dialogs-and-menus-initial-open-lags-freezes/56842/2 A fellow user seems to have narrowed the issue to this package. I am also linking my issue that I posted on MUI's github for reference. |
I'm not quite sure if the issue is identical, as this particular issue seems to be a case where the exported variable is incorrectly wrapped (since it's actually a different Regardless, the slowdowns when using Material UI 5 (read: emotion) in combination with Meteor (read: reify) seem to be caused by exports in the |
Meteor + MUI5 is unusable due to this issue. It takes 600ms for me to render a simple form dialog, while other built systems doesn't have this issue. |
Hi, reify is not part of Meteor officially but we use it to compile our code so we (Meteor) are going to take a look at this issue soon. Keep following here or in the Forums for updates. |
Hi all, could you give a try at Meteor 2.5.2-beta.0? More details here. |
Meteor 2.5.2 includes this fix. meteor#1 |
I am using reify 0.20.12 from Meteor and am importing vec3 from gl-matrix.
My issue is that this function:
once run through reify becomes:
I suspect the issue triggered because another
len
is later exported :being a heavy 3D application, normalize is called 100s or 1000s of times per frame and this needless callback is really killing performance. Is this expected? Any way to avoid it?
The text was updated successfully, but these errors were encountered: