The feedback you are referring to was regarding if semicolons should be required in class bodies after methods, setters and getters, which didn't appears to introduce any additional hazards at the time. Async, computed property name and uninitialized class values were not heavily considered at the time.

No, it wasn't. The feedback I'm referring to was regarding whether semicolons should be required in class bodies after class fields. I've talked to a lot of people about this specific decision.

perhaps if everything being shoved in class bodies now were on the table during the initial discussions you mentioned it would have been easier to take a harder stance on semicolon-separators-in-class-bodies will be required.

I spent some time playing with Matter.js, a JavaScript-powered 2D physics engine. Overall, pretty fun stuff. This article shares some highlights from my time spent with Matter.js, but I wouldn’t consider it a from-the-ground-up tutorial. If that’s what you’re looking for, the official Wiki is a good starting point. There’s also this tutorial series that I found useful.

My first Matter.js project was mostly just an excuse to throw a bunch of bodies around and see the physics in action. Here it is.

See the Pen Browser Crash by Will Boyd (@lonekorean) on CodePen.

There is a bit of setup to do before you can start adding bodies and tossing them around. Don’t worry, it’s not so bad — you can mostly just treat it as boilerplate code and add in whatever options you need. Here’s a slightly modified version of the setup code used in the demo above.