Im facing the same issue with tfjs-core 3.18.0 when using it with reactjs. None of the above response have resolved the issue.

[pistolla]

Im facing the same issue with "@tensorflow/tfjs-core": "^3.18.0" when using it with reactjs. None of the above response have resolved the issue.

Originally posted by @pistolla in #4296 (comment)

[rthadur]

These are the working examples https://github.com/tensorflow/tfjs-examples/tree/master/react-native/image-classification for react native , can you try running them ? Thank you

[pistolla]

Thanks for the reply. The issue im facing is not exactly related to reactjs framework. I have issue with weakmap used in tfjs and tfjs-core. They are inaccessible, in that, even using browser console i can dump the content of weakmap _tfengine.state.tensorInfo but when i try to reference a specific key the response is undefined. I'm wondering if this is a case of browser implementation of the weakmap or what is wrong? check the screenshots i shared in the referenced issue. I don't understand. Take a few minutes and check them. Thanks.

[rthadur]

is it possible to share reproducible code either codepen or git repo ? Thank you

[google-ml-butler]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you.

[google-ml-butler]

Closing as stale. Please @mention us if this needs more attention.

[google-ml-butler]

Are you satisfied with the resolution of your issue?
Yes
No

[vanessaZh]

Thanks for the reply. The issue im facing is not exactly related to reactjs framework. I have issue with weakmap used in tfjs and tfjs-core. They are inaccessible, in that, even using browser console i can dump the content of weakmap _tfengine.state.tensorInfo but when i try to reference a specific key the response is undefined. I'm wondering if this is a case of browser implementation of the weakmap or what is wrong? check the screenshots i shared in the referenced issue. I don't understand. Take a few minutes and check them. Thanks.

i found vue3 is not incompatible and will cause the same problem. the error seems to be caused by the fact that Vue3 wrapped my model attribute in a Proxy object