You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As LazyMotion uses the Context API under the hood and a useEffect to load features and update the state, it means that wrapping your entire app or a portion of it will inevitably lead to useless re-renders. This is the case because the code will also run on pages where there is no m element.
Would it be more performant to wrap each m element, even if that means reloading the futures again every time the component renders because the state is not available globally?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As LazyMotion uses the Context API under the hood and a useEffect to load features and update the state, it means that wrapping your entire app or a portion of it will inevitably lead to useless re-renders. This is the case because the code will also run on pages where there is no m element.
Would it be more performant to wrap each m element, even if that means reloading the futures again every time the component renders because the state is not available globally?
Beta Was this translation helpful? Give feedback.
All reactions