three.js versioning in package file about wwobjloader HOT 5 CLOSED

Wouldn't i t make more sense to define three-js like ^0.128.1 and only upgrade it if the api / base class changes. I think there was a change needed after 128, that's why it is at 0.133.1 , but I don't remember exactly right now. Next jump will be to be to 137+ (import maps) once I have finished the work on three-wtm.

from wwobjloader.

The version in question isn't the issue, it's that WWOBJLoader requires three as a regular dependency instead of a peer, so the three that is in this package file is also installed separately from the three in my package file. It would be more practical if this library included three as a peer+dev

from wwobjloader.

It would be more practical if this library included three as a peer+dev

Ok, got it. That makes sense.

from wwobjloader.

I guess same goes for three-wtm as well since it looks to be the same setup. Thanks again for the work on these loaders, they sure beat me clumsily hand rolling my own

from wwobjloader.

@geoff-harper I consider this resolved. 5.0.0 will be released soon. #68 needs to be implemented, then it is should be ready.

from wwobjloader.