Description

This issue contains the discussion for the new major version v5.

Suggested solution

• Refactor useGLTF and useFBX to adapt to core's useLoader refactor (related Several composables are not truly composables. tres#922 feat(loader)!: refactor useLoader to a true composable tres#959)
• Refactor abstractions dependent on core's useTexture refactor (related Several composables are not truly composables. tres#922 feat(useTexture)!: refactor to be a real composable with a state tres#949)
• Drop UMD Support Drop UMD Support #608
• Accumulative shadows feat(AccumulativeShadows): add component, demo, docs #558
• Point material feat(PointMaterial): add component, demo, docs #545
• ScreenQuad feat(ScreenQuad): add component, playground, docs #530
• CubicBezierline feat(CubicBezierLine): add component, demo, docs #546
• QuadraticNezierLine feat(QuadraticBezierLine): add component, demo, docs #548
• Bounds feat(Bounds): add component, demo, docs (#408) #568
• CircleShadow feat(CircleShadow): add component, demo, docs #549
• Stage feat(Stage): add component, demo, docs #572
• LOD feat(LOD): add component, playground, docs #524
• useIntersect feat(useIntersect): add function, demo, docs #550

Alternative

No response

Additional context

No response

Validations

• I agree to follow this project's Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.