Compare the user’s version of three.js with our patched and bundled version to ensure that no differences in the scene graph or object hierarchy occur after calling loadGLTF. Our types should be applicable and provide an accurate representation of the runtime.
Possible approaches:
-
Validation during the plugin build: Check if the versions match known compatible ones. (Not recommended, as predicting future changes is difficult, and we would need to constantly keep up with new three.js releases by adding tests and making frequent updates.)
-
Documenting tested compatibility: List known compatible versions in README.md (or later in the wiki). (Recommended. If someone uses a "too new" version that we haven't tested yet, it's their responsibility. However, in most cases, it should work fine since gltfLoader rarely undergoes significant changes.)
Compare the user’s version of
three.jswith our patched and bundled version to ensure that no differences in the scene graph or object hierarchy occur after callingloadGLTF. Our types should be applicable and provide an accurate representation of the runtime.Possible approaches:
Validation during the plugin build: Check if the versions match known compatible ones. (Not recommended, as predicting future changes is difficult, and we would need to constantly keep up with new
three.jsreleases by adding tests and making frequent updates.)Documenting tested compatibility: List known compatible versions in
README.md(or later in the wiki). (Recommended. If someone uses a "too new" version that we haven't tested yet, it's their responsibility. However, in most cases, it should work fine sincegltfLoaderrarely undergoes significant changes.)