reinstate w/h shorthand properties

[wouterlucas]

Warning - breaking changes

width and height properties have been renamed to short hand form w and h to match upstream usage.
This includes:

• Node props and Node Text Props (including animations)
• Dimensions returned in events
• Shader properties
• Texture dimension properties

[michielvandergeest]

@wouterlucas I prefer events to report w and h as well and keep things consistent

[chiefcll]

Why width and height are preferable

• Clarity and Self-Documentation
  width and height are immediately obvious to anyone reading the code — including people brand-new to the project or even to programming.
  w and h require context: to you and your team it’s second nature, but to a new contributor, they could mean “weight” or “window” or something else.

• Consistency with the JavaScript / DOM ecosystem
  The HTML DOM, CSSOM, Canvas API, and almost every JS graphics API use width and height.
  Sticking with these terms reduces mental switching costs when moving between different parts of a codebase or different frameworks.

• Better for tooling and searchability
  Searching the codebase for width finds all relevant references — searching for w often returns noise (variables named w, temporary counters, loop vars, etc.).
  Auto-complete in IDEs is more predictable and descriptive.

• Reduces “hidden shorthand” culture
  Short forms encourage devs to make similar abbreviations elsewhere (xPos → x, opacity → o, etc.), leading to an API that’s harder to read for anyone who didn’t grow up inside the codebase.

Might also want to let the Plex folks know you're breaking their upstream framework as well.

[wouterlucas]

Yeah good point - will let Plex know!

[michielvandergeest]

Nice work ❤️

I found a few minor errors, possibly the ones responsible for the failing VR tests?