Is there a process for merging with the three.js version? #33
Description
I noticed that the version of the CSM code which is distributed with three.js (as an addon) is very out of date and contains at least one "showstopper" bug which has been fixed in this repo long ago.
There are quite a lot of other differences too.
Merging is not entirely trivial so I'm reluctant to do it manually, and I've not seen any automation in this regard.
Last but not least, due to the unfortunate shader injection situation, the shader code in this repo also needs to be updated because the light_fragment_begin shader code has had updates which have not been merged into this repo yet.
Do you have any stance on this? Are there any plans or strategies in play to keep the versions from diverging? Can we improve the situation somehow?