Skip to content
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

React Developer Tools react-router-dom e.hasOwnProperty is not a function, Cannot read property 'name' of undefined #17764

Closed
yrambler2001 opened this issue Jan 3, 2020 · 3 comments

Comments

@yrambler2001
Copy link

bug
Uncaught TypeError: Cannot read property 'name' of undefined
Uncaught TypeError: e.hasOwnProperty is not a function

infinite loading in component view
image

Reproduce:
use hook useRouter or HOC withRouter from react-router-dom and select component with hook/hoc in components view react developer tools
Issue is caused by not-bug hapijs/hapi#3280
(query object does not have constructor and does not have hasOwnProperty)

image
image
image

@JackPott
Copy link

JackPott commented Jan 3, 2020

I've suddenly started getting this error when clicking on certain components in the Components inspector too. Feels like something 'bad' in one of my comps, but I can't for the life of me find whats causing it, theres another Issue from yesterday for something similar. Has there been an update?

    at O (backend.js:1)
    at s (backend.js:1)
    at s (backend.js:1)
    at s (backend.js:1)
    at l (backend.js:1)
    at Object.inspectElement (backend.js:6)
    at t.<anonymous> (backend.js:6)
    at t.r.emit (backend.js:6)
    at backend.js:32
    at t (backend.js:8)```

@bvaughn
Copy link
Contributor

bvaughn commented Jan 3, 2020

Uncaught TypeError: e.hasOwnProperty is not a function

This has already been reported as #17761

Uncaught TypeError: Cannot read property 'name' of undefined

This has already been reported as #17754

A fix for both issues will release shortly. I'm going to close this issue since it's a duplicate 😄

@bvaughn
Copy link
Contributor

bvaughn commented Jan 3, 2020

FYI this issue should be fixed in v4.4 (released today)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants