motiondivision / motiondivision/motion
[BUG] Not part of the THREE namespace.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33.7k
- Forks
- 1.4k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 14
Description
-
Describe the bug
I have to extend some THREE components (boxGeometry, meshBasicMaterial, etc), otherwise it throws: "not part of the THREE namespace". -
CodeSandbox reproduction of the bug
https://codesandbox.io/p/github/Endrickmusic/framer-motion-ortho/master?import=true -
Steps to reproduce
A. Remove one of the extends in line 10 of Scene.jsx .
B. See error -
Detail log
Uncaught Error: R3F: BoxGeometry is not part of the THREE namespace! Did you forget to extend?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked CodeSandbox reproduction and inspect Scene.jsx, especially line 10 and the component extensions. Reproduce the namespace error after removing an extends entry, then trace the integration behavior to identify why the THREE component is rejected. Done means the reproduction works without those manual extensions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, three.js, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100