@driftengine/assets 4.7.0 → 4.7.2

package/dist/readModel.d.ts

@@ -149,6 +149,8 @@ export interface ModelImport {
  * whole call in a worker and keep the parse off the main thread.
  */
 export declare function readModel(source: ModelSource): Promise<ModelImport>;
+/** The separate levels of detail a bundle ships beside its model, finest first. */
+export declare function levelsBeside(model: string, names: readonly string[]): string[];
 /**
  * The collision hull a vehicle folder ships beside its model, or null.
  *
@@ -162,5 +164,4 @@ export declare function readModel(source: ModelSource): Promise<ModelImport>;
  * reader and no writer — a format decision about whether a hull is triangle soup or a set of
  * convex hulls, and not one an import should make in passing.
  */
-export declare function levelsBeside(model: string, names: readonly string[]): string[];
 export declare function colliderBeside(names: readonly string[]): string | null;

package/dist/readModel.js

@@ -383,19 +383,7 @@ function base64Bytes(base64) {
         out[i] = binary.charCodeAt(i);
     return out;
 }
-/**
- * The collision hull a vehicle folder ships beside its model, or null.
- *
- * **A convention, not a statement in any file**, which is why it is one named function instead of
- * a rule spread through the baker: a folder naming its hull differently gets no collider and the
- * baker says what it looked for, rather than leaving a consumer to wonder why physics has nothing
- * to work with.
- *
- * It is read by the ordinary reader and baked as its own asset. Carrying a hull *inside* the
- * model's own file would mean defining `COLL`, which is a declared FourCC with no payload, no
- * reader and no writer — a format decision about whether a hull is triangle soup or a set of
- * convex hulls, and not one an import should make in passing.
- */
+/** The separate levels of detail a bundle ships beside its model, finest first. */
 export function levelsBeside(model, names) {
     /*
      * `<name>_lod_<letter>.kn5` beside `<name>.kn5`, finest first, which is the order the letters
@@ -410,6 +398,19 @@ export function levelsBeside(model, names) {
         .sort((a, b) => a.match[1].toLowerCase().localeCompare(b.match[1].toLowerCase()))
         .map((entry) => entry.name);
 }
+/**
+ * The collision hull a vehicle folder ships beside its model, or null.
+ *
+ * **A convention, not a statement in any file**, which is why it is one named function instead of
+ * a rule spread through the baker: a folder naming its hull differently gets no collider and the
+ * baker says what it looked for, rather than leaving a consumer to wonder why physics has nothing
+ * to work with.
+ *
+ * It is read by the ordinary reader and baked as its own asset. Carrying a hull *inside* the
+ * model's own file would mean defining `COLL`, which is a declared FourCC with no payload, no
+ * reader and no writer — a format decision about whether a hull is triangle soup or a set of
+ * convex hulls, and not one an import should make in passing.
+ */
 export function colliderBeside(names) {
     return names.find((name) => name.toLowerCase() === 'collider.kn5') ?? null;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@driftengine/assets",
-  "version": "4.7.0",
+  "version": "4.7.2",
   "description": "Model readers and the streaming loader for the .drft container",
   "license": "Apache-2.0",
   "type": "module",
@@ -27,11 +27,11 @@
   ],
   "sideEffects": false,
   "dependencies": {
-    "@driftengine/drft": "4.7.0",
-    "@driftengine/texture": "4.7.0"
+    "@driftengine/drft": "4.7.2",
+    "@driftengine/texture": "4.7.2"
   },
   "peerDependencies": {
-    "@driftengine/core": "4.7.0"
+    "@driftengine/core": "4.7.2"
   },
   "author": "Drift Technologies",
   "repository": {

package/src/readModel.ts

@@ -523,19 +523,7 @@ function base64Bytes(base64: string): Uint8Array {
   return out;
 }
 
-/**
- * The collision hull a vehicle folder ships beside its model, or null.
- *
- * **A convention, not a statement in any file**, which is why it is one named function instead of
- * a rule spread through the baker: a folder naming its hull differently gets no collider and the
- * baker says what it looked for, rather than leaving a consumer to wonder why physics has nothing
- * to work with.
- *
- * It is read by the ordinary reader and baked as its own asset. Carrying a hull *inside* the
- * model's own file would mean defining `COLL`, which is a declared FourCC with no payload, no
- * reader and no writer — a format decision about whether a hull is triangle soup or a set of
- * convex hulls, and not one an import should make in passing.
- */
+/** The separate levels of detail a bundle ships beside its model, finest first. */
 export function levelsBeside(model: string, names: readonly string[]): string[] {
   /*
    * `<name>_lod_<letter>.kn5` beside `<name>.kn5`, finest first, which is the order the letters
@@ -556,6 +544,19 @@ export function levelsBeside(model: string, names: readonly string[]): string[]
     .map((entry) => entry.name);
 }
 
+/**
+ * The collision hull a vehicle folder ships beside its model, or null.
+ *
+ * **A convention, not a statement in any file**, which is why it is one named function instead of
+ * a rule spread through the baker: a folder naming its hull differently gets no collider and the
+ * baker says what it looked for, rather than leaving a consumer to wonder why physics has nothing
+ * to work with.
+ *
+ * It is read by the ordinary reader and baked as its own asset. Carrying a hull *inside* the
+ * model's own file would mean defining `COLL`, which is a declared FourCC with no payload, no
+ * reader and no writer — a format decision about whether a hull is triangle soup or a set of
+ * convex hulls, and not one an import should make in passing.
+ */
 export function colliderBeside(names: readonly string[]): string | null {
   return names.find((name) => name.toLowerCase() === 'collider.kn5') ?? null;
 }