@gltf-transform/core - npm Package Compare versions

Comparing version 3.4.2 to 3.4.3

dist/io/reader-context.d.ts

@@ -5,3 +5,3 @@ import type { JSONDocument } from '../json-document.js';
 /**
- * Model class providing glTF-Transform objects representing each definition in the glTF file, used
+ * Model class providing glTF Transform objects representing each definition in the glTF file, used
  * by a {@link GLTFReader} and its {@link Extension} implementations. Indices of all properties will be
@@ -8,0 +8,0 @@ * consistent with the glTF file.

dist/properties/accessor.d.ts

@@ -57,3 +57,3 @@ import { Nullable, PropertyType, TypedArray } from '../constants.js';
  *
- * glTF-Transform does not expose many details of sparse, normalized, or interleaved accessors
+ * glTF Transform does not expose many details of sparse, normalized, or interleaved accessors
  * through its API. It reads files using those techniques, presents a simplified view of the data
@@ -60,0 +60,0 @@ * for editing, and attempts to write data back out with optimizations. For example, vertex

dist/properties/buffer.d.ts

@@ -10,3 +10,3 @@ import { Nullable, PropertyType } from '../constants.js';
  * glTF 2.0 has three concepts relevant to binary storage: accessors, buffer views, and buffers.
- * In glTF-Transform, an {@link Accessor} is referenced by any property that requires numeric typed
+ * In glTF Transform, an {@link Accessor} is referenced by any property that requires numeric typed
  * array data. Meshes, Primitives, and Animations all reference Accessors. Buffers define how that
@@ -23,5 +23,5 @@ * data is organized into transmitted file(s). A `.glb` file has only a single Buffer, and when
  *
- * Buffer Views define how Accessors are organized within a given Buffer. glTF-Transform creates an
+ * Buffer Views define how Accessors are organized within a given Buffer. glTF Transform creates an
  * efficient Buffer View layout automatically at export: there is no Buffer View property exposed
- * by the glTF-Transform API, simplifying data management.
+ * by the glTF Transform API, simplifying data management.
  *
@@ -28,0 +28,0 @@ * Usage:

dist/properties/texture.d.ts

@@ -11,3 +11,3 @@ import { Nullable, PropertyType, vec2 } from '../constants.js';
  *
- * Textures in glTF-Transform are a combination of glTF's `texture` and `image` properties, and
+ * Textures in glTF Transform are a combination of glTF's `texture` and `image` properties, and
  * should be unique within a document, such that no other texture contains the same
@@ -14,0 +14,0 @@ * {@link Texture.getImage getImage()} data. Where duplicates may already exist, the `dedup({textures: true})`

package.json

 {
 	"name": "@gltf-transform/core",
-	"version": "3.4.2",
+	"version": "3.4.3",
 	"repository": "github:donmccurdy/glTF-Transform",
@@ -49,3 +49,3 @@ "homepage": "https://gltf-transform.dev/",
 	"dependencies": {
-		"property-graph": "^1.2.0"
+		"property-graph": "^1.3.1"
 	},
@@ -55,3 +55,3 @@ "mangle": {
 	},
-	"gitHead": "af29fb35bad5b7996828206a5797ddabecb259d9"
+	"gitHead": "701a51849636e2cf9c2d10e0f3faf13b4a808352"
 }

README.md

@@ -7,3 +7,3 @@ # @gltf-transform/core
 
-Part of the glTF-Transform project.
+Part of the glTF Transform project.
 
@@ -10,0 +10,0 @@ - GitHub: https://github.com/donmccurdy/glTF-Transform

src/io/reader-context.ts

@@ -18,3 +18,3 @@ import type { JSONDocument } from '../json-document.js';
 /**
- * Model class providing glTF-Transform objects representing each definition in the glTF file, used
+ * Model class providing glTF Transform objects representing each definition in the glTF file, used
  * by a {@link GLTFReader} and its {@link Extension} implementations. Indices of all properties will be
@@ -21,0 +21,0 @@ * consistent with the glTF file.

src/io/reader.ts

@@ -124,3 +124,3 @@ import { GLB_BUFFER, PropertyType, TypedArray, mat4, vec3, vec4, ComponentTypeToTypedArray } from '../constants.js';
 
-		// glTF-Transform's "Texture" properties correspond 1:1 with glTF "Image" properties, and
+		// glTF Transform's "Texture" properties correspond 1:1 with glTF "Image" properties, and
 		// with image files. The glTF file may contain more one texture per image, where images
@@ -138,3 +138,3 @@ // are reused with different sampler properties.
 
-			// glTF Image corresponds 1:1 with glTF-Transform Texture. See `writer.ts`.
+			// glTF Image corresponds 1:1 with glTF Transform Texture. See `writer.ts`.
 			if (imageDef.extras) texture.setExtras(imageDef.extras);
@@ -141,0 +141,0 @@

src/io/writer.ts

@@ -378,3 +378,3 @@ import {
 
-		// glTF-Transform's "Texture" properties correspond 1:1 with glTF "Image" properties, and
+		// glTF Transform's "Texture" properties correspond 1:1 with glTF "Image" properties, and
 		// with image files. The glTF file may contain more one texture per image, where images
@@ -381,0 +381,0 @@ // are reused with different sampler properties.

src/properties/accessor.ts

@@ -61,3 +61,3 @@ import { Nullable, PropertyType, TypedArray } from '../constants.js';
  *
- * glTF-Transform does not expose many details of sparse, normalized, or interleaved accessors
+ * glTF Transform does not expose many details of sparse, normalized, or interleaved accessors
  * through its API. It reads files using those techniques, presents a simplified view of the data
@@ -64,0 +64,0 @@ * for editing, and attempts to write data back out with optimizations. For example, vertex

src/properties/buffer.ts

@@ -12,3 +12,3 @@ import { Nullable, PropertyType } from '../constants.js';
  * glTF 2.0 has three concepts relevant to binary storage: accessors, buffer views, and buffers.
- * In glTF-Transform, an {@link Accessor} is referenced by any property that requires numeric typed
+ * In glTF Transform, an {@link Accessor} is referenced by any property that requires numeric typed
  * array data. Meshes, Primitives, and Animations all reference Accessors. Buffers define how that
@@ -25,5 +25,5 @@ * data is organized into transmitted file(s). A `.glb` file has only a single Buffer, and when
  *
- * Buffer Views define how Accessors are organized within a given Buffer. glTF-Transform creates an
+ * Buffer Views define how Accessors are organized within a given Buffer. glTF Transform creates an
  * efficient Buffer View layout automatically at export: there is no Buffer View property exposed
- * by the glTF-Transform API, simplifying data management.
+ * by the glTF Transform API, simplifying data management.
  *
@@ -30,0 +30,0 @@ * Usage:

src/properties/texture.ts

@@ -14,3 +14,3 @@ import { Nullable, PropertyType, vec2 } from '../constants.js';
  *
- * Textures in glTF-Transform are a combination of glTF's `texture` and `image` properties, and
+ * Textures in glTF Transform are a combination of glTF's `texture` and `image` properties, and
  * should be unique within a document, such that no other texture contains the same
@@ -17,0 +17,0 @@ * {@link Texture.getImage getImage()} data. Where duplicates may already exist, the `dedup({textures: true})`

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1507049

Dependency changes

• Updatedproperty-graph@^1.3.1