I just updated THREE from the last version recorded as three.js in NPM to the latest one, so 0.77.0 to 0.122.0. Suddenly, something that had been working perfectly until now stopped doing so. I was using some custom classes inheriting from THREE classes like Mesh, Group etc. Nothing to do with the graphics themselves, really, they mostly provided convenience methods to access or edit properties. Now however the same objects give me a series of errors like:
three.js:5292 THREE.Object3D.add: object not an instance of THREE.Object3D
Is this an expected change in behaviour? Should I just change my code to account for this or what?
You should always configure a project with all dev dependencies and not assume certain stuff is globally installed on a system. Anyway, I’ve added latest http-server myself to package.json. After running the command, everything seems to work fine:
Ok, thanks, so there’s just something wrong in my installation for some reason. Good to know. And yeah, for http-server I’ve used it globally for so long I forgot about it in this repo.