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

DevTools can't inspect object without prototype #17754

Closed
yume-chan opened this issue Jan 2, 2020 · 4 comments · Fixed by #17757
Closed

DevTools can't inspect object without prototype #17754

yume-chan opened this issue Jan 2, 2020 · 4 comments · Fixed by #17757

Comments

@yume-chan
Copy link

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

  1. Select a component
  2. The right panel (property panel?) always shows Loading...
  3. The following error is printed to the console.
backend.js:1 Uncaught TypeError: Cannot read property 'name' of undefined
    at O (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)

image

I don't know why you minify the output, but the call stack points to here:

} else if (data.constructor.name === 'ArrayBuffer') {

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

https://codesandbox.io/s/falling-wave-1j0qe

What is the expected behavior?

React DevTools displays the props of the selected component.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

React 16.12.0
Chrome 79.0.3945.88
IDK

@bvaughn
Copy link
Contributor

bvaughn commented Jan 2, 2020

Thanks for the repro case.

@bvaughn
Copy link
Contributor

bvaughn commented Jan 3, 2020

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

@PatNeedham
Copy link

What is the release process like? I still see 4.3.0 on the Chrome web store: https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi
image

@bvaughn
Copy link
Contributor

bvaughn commented Jan 6, 2020

The release process is...the newer version will go live once Chrome reviews it. They seem to have fallen pretty far behind around the hoildays.

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

Successfully merging a pull request may close this issue.

3 participants