Oh it seems there are a lot of references... Are we convinced we'd like to exclude browser commands from element? @christian-bromann

Are we convinced we'd like to exclude browser commands from element?

Yes, I don't expect anyone to use it because it would throw an error at runtime. The build shows one error caused by:

I suggest the following change:

-     if (!(scope as WebdriverIO.Element).elementId) {
+     if (!('elementId' in scope)) {
        return scope.execute(selector as any, referenceId)
    }

Note: if a core package fails to compile you usually get a ton of other TS errors as well since it won't be able to access types of that core package.

Note: if a core package fails to compile you usually get a ton of other TS errors as well since it won't be able to access types of that core package.

Yes there was just one place where it should be changed. Thank you for the explanation. It worth to know!