Not Compatible with OpenUI5 / DOMException: Failed to execute 'removeChild'

[promosjotte]

Issue details

Development with OpenUI5 framework works not with BS. There is an error Uncaught DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

Steps to reproduce/test case

Use BS with any OpenUI5 App

Please provide necessary steps for reproduction of this issue, or better the reduced test case (without any external dependencies).

Fixed it localy in \node_modules\browser-sync\client\dist\index.js with a try/catch (line 1952):

        /**
         * Now remove the element after the given timeout
         */
        switchMap_1.switchMap(function (_a) {
            var event = _a[0], options = _a[1], element = _a[2], document = _a[3];
            return timer_1.timer(event[1] || 2000).pipe(tap_1.tap(function () {
                element.style.display = "none";             
                if (element.parentNode) {
                    //try catch is the fix
                    try
                    {
                        document.body.removeChild(element); 
                    }
                    catch(e)
                    {
                        console.log("this helps")
                    }

                }
            }));

Please specify which version of Browsersync, node and npm you're running

• Browsersync [ 2.24.7 ]
• Node [ 8.9.3 ]
• Npm [ 5.5.1 ]

Affected platforms

• [] linux
• [X] windows
• [ ] OS X
• [ ] freebsd
• [ ] solaris
• [ ] other (please specify which)

Browsersync use-case

• [ ] API
• [X] Gulp
• [ ] Grunt
• [ ] CLI

If CLI, please paste the entire command below

for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync

with gulp:

var browserSync = require("browser-sync");

browserSync({
    port: 9000,
    server: {
        baseDir: `./app`
    }
});

[jonaszuberbuehler]

As a workaround you could disable notifications (option notify:false).

[promosjotte]

@jonaszuberbuehler thanks, works! This is definitely a better workaround.