Cho, Yongjoon but he assigns them to the local state in the constructor so he would have to unmount and remount them all the time to have this bug with props.
Saša Fišter i would put a console.log(props) into the constructor and check how often if it gets called. since I don't know the context of the component.
based on that I would use a binary elimination process where I would try to narrow down the problem.
Saša Fišter so the constructor passes zero -> how often does it get called ? maybe the parent un and remounts the child all the time ? because the props are passed in the constructor and you hopefully use state for the internal representation.
Saša Fišter I would have to really check out the code and debug it, there are several possibilities, from caching to different compiling and so on. And I am working on 3-4 projects at the moment so I barely make time to write and read @ hashnode
Saša Fišter np, sorry I can't be of more help. One last thought check the building process if you have the same behaviour if you use the compiled output instead the webpack build (I assume webpack). And if it still works locally maybe you can diff against the downloaded js compile files to see if there's a difference.