Closed looeee closed 1 year ago
are you using it as a part of the repo? i always just use it with npx and then it cant be confused with any other react version in node-modules
Yeah, using it via npx works fine and that's what I've been doing. However when working on a client project I prefer to use version control for all tooling. In this case I want the client to be able to update models once I've passed over the project - even if they don't do that for two years I'd rather all the versions are locked so that everything still just works.
i updated it to react 17
When I run
npm i -D gltfjsx
I get the following error:If I install with
--legacy-peer-deps
then it installs OK but runningnpx gltfjsx model.glb
gives a whole load of errors including:So presumably it's now complaining that I've forced an install of both React@16 (peerdep) and React@17 (standard dep).