NotFoundError: Node.removeChild: The node to be removed is not a child of this node

[razzeee]

Describe the bug When logged into the admin interface, we get an error shown at the top

To Reproduce

• Checkout https://github.com/xbmc/kodi-tv/tree/main
• Run npm i
• Run npm start
• Goto http://localhost:8000/admin/#/
• You should see an error - there also are errors in the start console

 WARNING  Compiled with 1 warning                                                                                                                                        
⠀
 warning  in ./node_modules/gatsby-plugin-decap-cms/gatsby-browser.js
⠀

Expected behavior Shouldn't show the error - sub pages get broken and also show the header in the middle of the page

Screenshots

Applicable Versions:

• Decap CMS version: decap-cms-app@3.1.1
• Git provider: github
• Browser version: Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0

CMS configuration

https://github.com/xbmc/kodi-tv/blob/main/static/admin/config.yml
...

[ProfYaffle]

FWIW on this, I've just tried (everything fully patched and upgrade beforehand - yes, I know "latest" isn't a version, but there are too many variables at play here):

• Ubuntu 22.04.4 physical machine #⁠1 - Chrome, Firefox native, Firefox Snap, Opera
• Ubuntu 22.04.4 physical machine #⁠2 - Chrome, Firefox Snap
• Ubuntu 22.04.4 VM (Ubuntu 22.04.4 #⁠1 host, Virtualbox) - Chrome, Firefox Snap
• Windows 10 VM (Ubuntu 22.04.4 #⁠1 host, Virtualbox) - Chrome, Edge, Firefox
• Windows 10 VM (Ubuntu 22.04.4 #⁠2 host, virt-manager) - Chrome, Edge, Firefox
• Windows 11 physical - Chrome, Firefox, Opera
• Android 14 physical - Chrome, Firefox, Opera, DuckDuckGo

I've also toggled VPN on/off where applicable (Opera), I've used private/incognito tabs, I've switched off my PiHole and also toggled between cellular and LAN to eliminate both local config and ISP issues. Most of these devices have never been used to access the CMS before, so there should be no cached... well, anything (plus several of these were refreshed or clean browser installations as well).

All failed with (browser-specific presentation variations of) the same error, as above. It's not looking like a client error, then, as I think that comprehensively eliminates most variables (including browser engine).

[razzeee]

As far as I can tell this was introduced with 3.1.0 - we've reverted to the version before that now and it started to work again.