TypeError: Cannot read properties of undefined (reading 'schemaChange') about aframe-inspector HOT 4 CLOSED

Since aframevr/aframe#5426
The error is now

Uncaught (in promise) TypeError: this.schema[n] is undefined

from aframe-inspector.

@vincentfretin I think this might be due to server-side caching by jsdelivr, as the error in question should not be possible with the check in place. What the debugger shows is the source mapped version, but when I load the aframe-master.min.js from cdn.jsdelivr.net manually I still see the old incomplete check in place...

I assume this will resolve itself in due time, though no idea how long it might be cached for. Replacing it with an explicit link to the latest commit on master at least shows that the error is gone with the fix:

<script src="https://cdn.jsdelivr.net/gh/aframevr/aframe@84bdb3cf4bdba86a20c603f792e283ca13bfba20/dist/aframe-master.min.js"></script>

from aframe-inspector.

Seems the cache might either be 12 hours or 7 days, according to the docs (https://www.jsdelivr.com/documentation#id-caching). I would assume 12 hours, though seeing how master is a fallback for latest in the case of GitHub it might follow the same cache duration(?)

And for context, while aframevr/aframe#5426 resolves the issue, the reason this bug surfaced in the first place is due to the following change in A-Frame: aframevr/aframe@924dc00, see aframevr/aframe#5425 for discussion. While the exception might be gone additional/incorrect component updates during initialization do still take place. Not sure if there is any negative impact on the inspector and/or example scene, but a heads up in case you notice anything.

from aframe-inspector.

Thank you. Good thing to know about the cache duration, I'll keep that in mind next time.
I'll close then.

from aframe-inspector.