josephrocca

Ah yeah, good point! If it isn't shipping with it then that makes sense :+1:

@domenic Ah, sorry about that! I've edited the question with a new minimal reproduction of the *actual* issue. I initially made some mistakes while chiseling it down to a minimal...

@crowlKats Wondering if there are any updates on this yet? A super rough guess at an ETA would be great if possible - e.g. "*maybe* some time in 2023". (Please...

@crowlKats Thanks for the update! I think I'm at risk of raising points that you and everyone on the team already understand very well, but: > this isn't a feature...

@crowlKats Could/should this perhaps be done lazily? So we keep this pull request, but then add another which optimises it by saving the transpiled JS code to `$NAME/versions/$VERSION/stripped/$FILEPATH.json`, and of...

Just want to chime in here to say I agree that: * Unintentional leaks are definitely an issue worth trying to solve. * It's probably not a good idea to...

@AdaRoseCannon Has eye tracking been discussed lately? Seems like [the last discussion](https://github.com/immersive-web/proposals/issues/25) was back in 2018? I'm guessing that eye and face tracking will hit "mass-market" devices in the next...

@cabanier Eye tracking would be a good start, but my particular use case needs full face tracking - to map facial expressions onto the user's avatar. As mentioned, I think...

@cabanier Do you mean like the above-mentioned iOS ARKit? As mentioned, that API exposes 52 blend shapes. Android's ARCore has the Augmented Face API exposes a face mesh as you...

Maybe worth mentioning: This is also blocking npm AWS SDK usage. I wonder if there's any way to polyfill this with something like `npm:node-forge` in the meantime?