Yuncheng Lu

Hey @etrepum @zurfyx I have a question regarding this change. [Here](https://github.com/facebook/lexical/blob/960adf903067747cb3d1ef7389e32bb5f34f9072/packages/lexical/src/LexicalNode.ts#L412) we have an invariant that all nodes have to implement `getType`. Along with this PR, do we have to...

> The data returned by $config is used to implement a boilerplate static getType for backwards compatibility when the node is registered with an editor. Yes, but I see in...

> getType is only called there when the node class directly implements it (the hasOwn check) and it is not one of the three abstract base classes (DecoratorNode, ElementNode, and...

> getType is only called there when the node class directly implements it (the hasOwn check) and it is not one of the three abstract base classes (DecoratorNode, ElementNode, and...

> Hard to say what the right workaround would be without knowing exactly how far Meta's implementation strays from the standard but if it respects the prototype chain correctly then...

How about we have two separate methods, (For instance method, I believe meta behaves the same): ```ts function hasOwnStaticMethod(o, k) { return (Object.prototype.hasOwnProperty.call(o, k) && o[k as keyof typeof o]...

Regarding the clone warning, I debugged for a while and I don't think I can change the behavior at Meta. Since it's an invariant in the dev environment, it will...