revert: temporarily undo Locker-specific logic

Author: wjhsf

packages/@lwc/engine-core/src/framework/invoker.ts

@@ -11,7 +11,7 @@ import { addErrorComponentStack } from '../shared/error';
 import { evaluateTemplate, setVMBeingRendered, getVMBeingRendered } from './template';
 import { runWithBoundaryProtection } from './vm';
 import { logOperationStart, logOperationEnd, OperationId } from './profiler';
-import { LightningElement } from './base-lightning-element';
+import type { LightningElement } from './base-lightning-element';
 import type { Template } from './template';
 import type { VM } from './vm';
 import type { LightningElementConstructor } from './base-lightning-element';
@@ -58,9 +58,11 @@ export function invokeComponentConstructor(vm: VM, Ctor: LightningElementConstru
         // the "instanceof" operator would not work here since Locker Service provides its own
         // implementation of LightningElement, so we indirectly check if the base constructor is
         // invoked by accessing the component on the vm.
-        const isInvalidConstructor = lwcRuntimeFlags.LEGACY_LOCKER_ENABLED
-            ? vmBeingConstructed.component !== result
-            : !(result instanceof LightningElement);
+        // TODO [W-17769475]: Restore this fix when we can reliably detect Locker enabled
+        // const isInvalidConstructor = lwcRuntimeFlags.LEGACY_LOCKER_ENABLED
+        //     ? vmBeingConstructed.component !== result
+        //     : !(result instanceof LightningElement);
+        const isInvalidConstructor = vmBeingConstructed.component !== result;
 
         if (isInvalidConstructor) {
             throw new TypeError(