thebuggeddev/anatomy: a three.js 3D human anatomy explorer

What thebuggeddev/anatomy does and who it is for

The repository is described as an interactive 3D human anatomy explorer built with three.js. That description, plus the dependency list, is the whole of what the project states about itself. There is no feature page, no screenshot walkthrough and no list of anatomical systems covered.

The audience is narrow and specific. This is for a developer who wants to see how a three.js scene is mounted inside a vinext app that deploys to Cloudflare Workers, and who is willing to read the source because the README will not explain the model. It is not for a medical student looking for a study tool, and it is not for a team that needs a supported component with a versioned API. The repository gives no indication that either audience is served.

The dependency set tells you what kind of project it is. three 0.185.1 is the renderer. gsap is present for animation. lucide-react supplies icons. next 16.2.6 and react 19.2.6 sit underneath, with vinext 0.0.50 and wrangler 4.92.0 as the deployment path. That is a modern stack, pinned tightly, and it means the project inherits every constraint of the vinext starter it was built from.

The vinext starter underneath the 3D scene

The README is the starter's README, not the explorer's. That is the single most important fact about this repository. The quick start, the workspace auth headers, the ChatGPT sign-in helpers and the D1 example all describe the vinext-starter template. The package name in package.json is site-creator-vinext-starter, which confirms the origin.

So the architecture has two layers. The bottom layer is the starter: a vinext app that runs on Cloudflare Workers, with an optional D1 database and Drizzle ORM, and a Vite config that simulates declared bindings for local development. The top layer is whatever thebuggeddev/anatomy adds: the three.js scene, the animation, the interface around the model.

What the README documents about the bottom layer is concrete. Site code lives under app/. The .openai/hosting.json file declares optional Sites D1 and R2 bindings. db/schema.ts starts intentionally empty. examples/d1/ holds an optional D1 example surface. drizzle.config.ts supports local migration generation. The starter explicitly does not use wrangler.jsonc, which is worth noting because most Cloudflare Workers projects do.

The top layer is undocumented. Nothing in the README describes the anatomy model, how it is loaded, whether it is a glTF file served from public/, or how the camera and controls are set up. The repository layout lists a public/ directory, which is the conventional place for such assets, but the README does not confirm it.

Installing thebuggeddev/anatomy and running it locally

The README gives a three-command quick start. Node.js 22.13.0 or newer is required, and the package.json engines field repeats that constraint.

npm install
npm run dev
npm run build

npm install pulls the full dependency set, including three, gsap and the Cloudflare toolchain. npm run dev starts local development. The package.json script wraps the vinext dev command and writes a wrangler log to .wrangler/wrangler.log, so if the dev server fails to start, that log file is the first place to look. npm run build verifies the vinext build output.

There is a test command that does more than run unit tests:

npm test

According to the README, this builds the starter and verifies its rendered loading skeleton. That is a build plus a single rendered-HTML assertion, not a test suite for the anatomy viewer. Do not read a passing npm test as evidence that the 3D scene works.

If you change the database schema, the starter provides a generation step:

npm run db:generate

That runs drizzle-kit generate against drizzle.config.ts. The schema file starts empty, so this command matters only if you add tables. The explorer itself does not obviously need a database, which makes the D1 and Drizzle layers dead weight unless you are extending the starter.

What you should see after npm run dev is a locally served vinext app. Whether that shows the anatomy model or the starter's default page is not stated anywhere in the README.

The licence is missing and that is a real problem

The licence is recorded as unknown. There is no LICENSE entry in the top-level repository listing, which shows .gitignore, .openai/, .vercelignore, README.md, app/, build/, db/, drizzle.config.ts, drizzle/, eslint.config.mjs, examples/, next.config.ts, package-lock.json, package.json, postcss.config.mjs, public/, scripts/, tests/, tsconfig.json, vercel.json, vite.config.ts and worker/.

No licence file means no granted rights. Under default copyright, a repository without a licence does not permit redistribution or derivative works, regardless of what the code is for. This is not a legal opinion and you should not treat it as one. It is a statement about what the repository does and does not contain.

For a personal experiment, this rarely matters. For anything that ships to users, it matters a great deal, and it is the first question to resolve. If you need a permissively licensed three.js anatomy reference, this is not currently one.

Where this is the wrong tool

The obvious failure mode is treating this as a product. There are no releases, no changelog, no version tags and no documented API. The version in package.json is 0.1.0 and the package is marked private, which is consistent with a personal project rather than a published library.

The second failure mode is the README mismatch. A developer who lands on the repository, reads the README and runs the quick start will get the vinext starter, including its ChatGPT sign-in helpers and its D1 example surface. None of that is about anatomy. If you were expecting a guide to the 3D model, you will not find one, and the time you spend looking for it is time the README actively misdirects.

The third is scope. A three.js anatomy explorer that runs in the browser is not a substitute for anything with validated anatomical data. The README says nothing about the source of the model, its accuracy, or how many structures it contains. If correctness matters for your use case, this project gives you no basis to judge it.

Finally, the stack is demanding for what it delivers. Node 22.13.0 or newer, vinext 0.0.50, Vite 8.0.13 and wrangler 4.92.0 are all recent and all pinned. A beginner who wants to learn three.js would be better served by a plain Vite plus three.js setup, because the Cloudflare and vinext layers add concepts that have nothing to do with rendering a model.

What to use instead, and how the approaches differ

The most direct alternative is three.js itself, without any framework. The official three.js examples include an interactive glTF viewer that loads a model, sets up a camera and adds orbit controls. The difference in approach is total: three.js gives you a renderer and a scene graph, and you write the application around it. thebuggeddev/anatomy gives you the application already assembled, but on top of a server framework you may not want.

If your goal is anatomy specifically rather than three.js, the honest answer is that a browser-based viewer is the wrong category. Reference material for anatomy is text and illustration, and this repository offers nothing comparable.

If your goal is the deployment target, a plain Cloudflare Workers project with the @cloudflare/vite-plugin and wrangler, without vinext, is a smaller surface. The starter's value is the D1 and Drizzle wiring and the ChatGPT sign-in helpers, and if you do not need those, you are carrying them for nothing.

The one case where this repository is genuinely useful is as a worked example. If you already know three.js and you want to see how someone else structured a scene inside a vinext app, reading app/ is faster than reading the vinext documentation and guessing.

Maintenance, upgrades and what to verify

The last push to the default branch was on 2026-08-09. That is recent enough that the code has not obviously been abandoned, but there are no releases, no issue activity and no roadmap, so there is no evidence of ongoing work beyond that single date. Do not assume fixes will arrive.

Upgrade cost is dominated by the pinned versions. next 16.2.6, react 19.2.6, three 0.185.1, vite 8.0.13, typescript 5.9.3 and vinext 0.0.50 are all exact or caret-pinned in package.json, and the lockfile is committed. Moving any one of them means checking the others, because vinext sits between Vite and Cloudflare Workers and its version is tied to both. React 19 and Next 16 are recent majors, so a downgrade is not a small operation either.

The Node engine constraint is a hard floor at 22.13.0. Older runtimes will fail before the build starts.

The licence question is unresolved and should be settled before you invest time. If the repository gains a licence file, that changes the picture; until then, treat the code as read-only reference.

Editorial conclusion

Use thebuggeddev/anatomy as a reference for wiring a three.js scene into a vinext and Cloudflare Workers app; the package.json pins three 0.185.1, gsap and lucide-react alongside the starter's Drizzle and wrangler stack. Do not adopt it if you need a documented install path, a stated licence or a stable API, because the README covers none of those. Verify three things before building on it: that the repository has a licence file, that app/ actually contains the anatomy scene rather than the starter's default page, and that npm run build succeeds under Node 22.13.0. The last push was on 2026-08-09, so the code has not moved since then.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. thebuggeddev/anatomy on GitHub