Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot read property '__emotion_real' of undefined

See original GitHub issue

So, we’re seeing this issue occasionally logged from Emotion. The component in question is defined as follows, where motion.div is a framer-motion animated element:

const StyledDiv = styled(motion.div)`
  backface-visibility: hidden;
  bottom: 0;
  ...

My best guess is that Emotion is trying to do business before framer-motion has made the element available. I don’t know whether it would be possible to suppress this noise … ?

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:11 (11 by maintainers)

Top GitHub Comments

1reaction

Andaristcommented, Mar 11, 2021

Heh, given Chrome 80+ pops up here this doesn’t sound like a Proxy-problem (or at least there has to be something else to it). There are a lot of things that can happen on the web though - including external browser extensions messing up with stuff, so I wouldn’t really be concerned much about it until you receive a real user report about this.

0reactions

Andaristcommented, Mar 12, 2021

Going to close this then - if you ever get a repro case for this then let me know. I’m quite curious regarding what is actually happening there.