v2

[nartc]

Hi folks, it's been a long time since I last updated on here.

V2 checklist

• Merge v2 branch
• Setup CONTRIBUTING guides and conventional commits
• Fix ng add
• Cannon documentation
• Postprocessing documentation
• Quarterly Roadmap

What have I been up to?

Mostly work. I started a branch to start working on angular-three v2 about 8 months ago but only recently have time to go back to actively working on it.

As of today (Jul 30 2024), 2.0.0-beta.277 has been released and it is extremely close to an official release of v2.

What are you doing now and shortly after v2?

As mentioned, I'm working on some logistics around the repo now to prepare for v2 support: purging issues, adding contributing guides, and whatnot. So apologize in advance if I close your issues without saying anything as my main focus now is to get v2 out (as I won't have time to support v1 anymore)

Right after v2, I'll put together some sort of Roadmap and Vision for the project. Then will work on promoting/documentation/video for Angular Three

FAQs

Why does v2 only support Angular 18+?

A recent change to how Angular triggers change detections for signal usage on the template has made me decided to make v18 the requirement for Angular Three. This allows me to drop substantial amount of code in the event system regarding to CD handling. With that said, v17 is technically usable with v2 but events might not update the template even if Signals are used.

ng add / Version conflicts

I admit that I did a horrible job of listing dependencies/peer dependencies for the project. This will change in v2 as everything will be listed as peerDependencies and clear version matrix.

Why does v2 take so long?

• Time
• Lots of changes happening to THREE.js as well as Angular
• And...it's just me

Why should I care about v2?

Honestly, I wouldn't expect anyone to care about v2 while the author/maintainer did such a horrible job on maintaining v1 of the library.

But after (working) seeing v2 in action, I think that you should give it a(nother) chance. Angular Three v2 is more stable and consistent than ever. It is as close to React Three Fiber as a THREE.js Angular Custom Renderer can be

I've ported countless examples from R3F to Angular Three v2 without much hassles. Things literally just fall into places.

How can I help?

If you've had issues with current Angular Three, please provide a stackblitz/repository so that I can try to reproduce it with v2 to confirm whether the issue is fixed or not. Otherwise, I can't really help.

Thank you all and I'll see you soon!