-
Notifications
You must be signed in to change notification settings - Fork 116
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
(in devtools tab): "Cannot find imported React library" #90
Labels
Comments
Somewhat related: #85 |
I'm getting the same error with my react app. |
Same here.. |
Same here |
Same for me. |
Same for me |
same here |
Tested with my projects and some react-powered websites. I'm getting the same error over and over again. |
Same for me |
Started for us after upgrade to React 16.
|
Same for me from react 16.x |
I'm getting this error on React
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:136 Uncaught RangeError: Maximum call stack size exceeded
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:136)
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:164)
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:164)
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:164)
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:164)
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:164)
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:164)
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:164)
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:164)
at parseProps (chrome-extension://aalppolilappfakpmdfdkpppdnhpgifn/backend/installHook.js:164)
The text was updated successfully, but these errors were encountered: