Three.js, semver, and addons

I’m mostly worried it’d do the opposite… We have a group of people maintaining *waves hands at all of this*, and the project has been structured in a way that supports this group’s work. Refactoring within a monorepo is easier than refactoring across multiple repos. I don’t imagine new contributors will come knocking as a result of any of the changes we’re discussing. So in practice I think it means a much smaller number of examples can be maintained, compared to what is (mostly successfully) maintained today.

But, I don’t think splitting core from examples is that necessary for semver? There are always going to be some examples where we care more about backward compat (OrbitControls, GLTFLoader) and others we don’t, or don’t yet (NodeMaterial, WebGPURenderer, …). It isn’t really a core vs. examples split.

1 Like