yep, seems like properties are being set on objects with only getters (instances).
Want to create an issue in github? the general solution would be to add getOwnPropertyDescriptor and check for writable or set , but maybe we can know beforehand that this object’s properties cannot be set.
Thank you @Deltakosh, side question, I reported some bugs for 4.1, some are already fixed, some I still try to reproduce in PG, how will npm release happen ? it will be fixed in for 4.2.alpha already or there will be 4.1.X releases ? as these bugs stop me from using 4.1
@Deltakosh nope still get error from npm Couldn’t find any versions for “@babylonjs/core” that matches “4.2.0-alpha.4”
as its dependency for inspector package