Console errors in Gutenberg 4.4.

[spacedmonkey]

Describe the bug
When I load gutenberg (4.4) in browser, I get a high number console errors. See screenshot.

To Reproduce
Steps to reproduce the behavior:

1. Open post edit screen in browser.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

• OS: OSX 10.13.6
• Browser Chrome
• Version: 70.0.3538.102

Additional context

• Gutenberg 4.4
• Yoast SEO 9.1

[tofumatt]

Any chance this is related to the recent React upgrade in #11840? cc @gziolo @youknowriad

[tofumatt]

Seems like this'd be fixed by #11360. These warnings don't imply anything is broken, for what it's worth. We just have to update our code to move to new APIs 😄

[youknowriad]

yes, it is related most of these are not coming from Gutenberg thought but more from plugins using deprecated APIs, Gutenberg itself is still using one or two deprecated APIs (the first warning I think). I'm closing this as a duplicate of #11360 but at the same time you should try to reach out the plugin authors using these too.

When it comes to the React update, it didn't add any new warnings to Gutenberg itself.

[spacedmonkey]

Looking into this, I am only seeing this when define( 'SCRIPT_DEBUG', true ); Even so, I get over 200 errors in console, seems like a lot. It seems to be linked to react-dom

[tofumatt]

Ah, noted, my bad.

[spacedmonkey]

Below is screenshots from a fresh install of WordPress 4.9.8 with no other plugins than gutenberg.

@youknowriad ^

[youknowriad]

Yes, nothing really concerning, but it should be fixed when #11360 is closed.