Viewer is currently broken and does not display any 3D content or profile information. about webxr-input-profiles HOT 6 CLOSED

I've figured out the issue, the three.js update did in fact break things since they switched to using bare imports for three in the example files. Adding an importmap in the index.html seems to fix this, but there's now other issues since we're jumping 20+ versions. I'll try and iron this out and PR.

Update: I currently have it working on Chrome, but since it requires import maps to function I'm unable to get it working on Firefox. Even using es-module-shims to try and polyfill it isn't working, seemingly due to an issue with how the polyfill handles cyclic dependencies or somesuch (I believe this issue is essentially what's happening here guybedford/es-module-shims#270). I'd say the easiest fix for now would just be to revert back to r113, or at least the latest version before they switched to using bare imports, which I believe is r127.

from webxr-input-profiles.

@toji Maybe we can downgrade three.js to 127?
I verified that it fixes the problem

from webxr-input-profiles.

Reverting to 127 sounds good to me.

from webxr-input-profiles.

Pushed 614bf32. Works locally, I'll keep an eye on it to see if it deploys properly.

from webxr-input-profiles.

Deployment looks good! I'll send in a PR later to address a couple API changes in three.js.

from webxr-input-profiles.

This is working now. Closing

from webxr-input-profiles.