you can try. i wouldn’t know where to start. this is a fairly standard project, like any other it has a package.json that lists the dependencies and uses a bundler, webpack in this case.
today everything is fetched from npm. npm (node package manager) does not work without node.
these are all the dependencies that are being used. maybe one or two might be umd or esm, you could copy them and go through a lot of pain and tooling (python, http servers, import maps, shims) and tell yourself that you’re doing it “manually”. but for the rest you need a bundler because they use common-js and require. even if all were pure esm, each dep has sub dependencies, the import map you’d have to make would get too complex to write by hand.
this was so much easier before when they had a global THREE object, but these days it’s like doctor cmda says, you either use the tools and get this done in 30 minutes, or you don’t and then suffer for 3+ days
Yeah, but I’m hoping that this is something I only need to do once, as I now have the solutions and know much better how those things work etc. But who knows, maybe more dependencies are heading our way in the future.
This should have been provided with the book’s code.