Jordan Pittman

@pzgz If you're still seeing issues with an npm-installed build that may mean the compiler is auto-vectorizing to at least AVX instructions for Oxide. I'll have to look and see...

Also I looked into it and the Celeron CPU does not support AVX *at all* — only SSE 4.2. (even tho it was released 10 *years* after the first processors...

Hey, as you've pointed out `@property` does require a default value (when syntax isn't `*`). Given that we want these values to be animatable (and explicitly designed stuff around making...

Gonna close this as a reproduction was not provided. Trying to create a reproduction ourselves from the information in an issue drastically increases the amount of time it takes for...

Thanks!

I've merged a fix for this which will be in v3.4.18. I _think_ we'll try to release it later this week maybe but I'm likely gonna try to get a...

I did some testing and the warning isn't present in: - Node v23.4+ - Node v24.0+ - Node v22.12+ - Node v20.19+ So for Node v23 the warning did get...

This will be fixed once 0.7.0 is out (aiming for some time next week but the release depends on a few more things). 👍

Sorry for getting to this so late. Seeing as you've updated to 0.6.11 I'm guessing this is no longer an issue for you. The error looks like Yarn wasn't resolving...

This will be fixed in the next release 👍