React-devtools: nativeObjectCreate

[LuisGonzaga]

Hello,
I am starting React & doing an "hello world", to my surprise I got the error described below, after searching the web (no similar results) I tested in FF and IE with no problems.
Then I disabled react-devtools 3.2.3 and everything was fine.

-> The script is very simple, just for the record:

-> error in Chrome 66.0.3359.181 (64 bits)
-> works fine in Firefox 60.0.1 (64-bit)

-> The error:
backend.js:708 Uncaught TypeError: Cannot read property 'nativeObjectCreate' of undefined
at Object. (backend.js:708)
at __webpack_require__ (backend.js:20)
at Object. (backend.js:690)
at __webpack_require__ (backend.js:20)
at Object. (backend.js:59)
at __webpack_require__ (backend.js:20)
at backend.js:40
at backend.js:43
(anonymous) @ backend.js:708
__webpack_require__ @ backend.js:20
(anonymous) @ backend.js:690
__webpack_require__ @ backend.js:20
(anonymous) @ backend.js:59
__webpack_require__ @ backend.js:20
(anonymous) @ backend.js:40
(anonymous) @ backend.js:43

[madlabman]

I have similar error using React dev tools in Chrome but it works fine in Firefox, check it out.

[ashsearle]

I've seen the same, and think this is the minimum required to reproduce:

• Create an HTML file containing:

<script src="https://unpkg.com/react@^16/umd/react.development.js"></script>

• Use "Open File..." in Chrome to open it using file:/// protocol.
• Inspect page
• Switch to React tab

Observe 1 JavaScript error. Switch to Console tab to view stack trace.

Serving the same file over http does not give any errors, just the "Waiting for roots to load..." message in React devtools.

[LuisGonzaga]

Well I believe that this is a conflict with other Extensions.
In my particular case I've disabled Ember Inspector, Ghost Text, "Screenshot, Annotate, & Screen Video Recorder..." plus "Sencha & Ext.js" ... and it started to work.

[ashsearle]

@LuisGonzaga I still see the same error even if I disable all other extensions.

Is it working when loading something as a local file:/// URL, or are you accessing stuff via http:// now?

[LuisGonzaga]

At this stage everything in the project is local. Restarting the browser or the PC may help to validate your changes.

[gaearon]

This is definitely a bug. Maybe something changed in how Chrome handles file://, or maybe we messed something up.