Object literals are evaluated property by property, left to right, by PropertyDefinitionEvaluation. Each form has semantics of its own.
Shorthand properties. { x } is { x: x }: it reads the binding x and creates an own data property. Nothing more.
Method syntax. { greet() {} } differs from { greet: function () {} } in two ways. DefineMethod calls MakeMethod, which records the object as the function's [[HomeObject]], so super.greet() works: it looks up the [[Prototype]] of the home object. And a method has no [[Construct]] and no prototype property, so new obj.greet() throws a TypeError. A function expression value is a constructor and can't contain super at all — that's a SyntaxError. Getters, setters, generator and async methods follow the method rules.
Computed keys. { [expr]: value } evaluates expr, then runs ToPropertyKey on it, then evaluates value. So a key object's toString runs before the value expression, and each property finishes before the next starts. Assignment is different: in obj[key] = value() the current spec delays ToPropertyKey until after the right-hand side, and Node.js 24 follows that order.
__proto__. A non-computed __proto__: value is special syntax: if the value is an object or null, it sets the new object's [[Prototype]], and otherwise it's ignored; either way no own property is created. Writing it twice is a SyntaxError. But a computed ['__proto__']: value and the shorthand { __proto__ } are ordinary definitions: they create an own property named "__proto__" and leave the prototype alone. JSON-parsed objects behave like the computed form.
Literal keys are normalised too: numeric literals become their canonical string (0x10 → '16', 1.0 → '1'), and duplicate keys are allowed, the last one winning — except __proto__.