@aura3d/rendering 1.5.2 → 2.0.0

package/dist/webgpu-device-entry.d.ts

@@ -0,0 +1,25 @@
+/**
+ * WS-2.2 — `WebGPUDevice` as its own entry point, so the barrel does not force it onto every bundle.
+ *
+ * ## The problem this solves
+ *
+ * `createRenderDevice` already loads the WebGPU device with `await import("./WebGPUDevice")`,
+ * deliberately, and says so: *"a statically imported branch is retained by bundlers even when the
+ * caller only ever asks for `webgl2`"*. That care was being undone one file away, because
+ * `packages/rendering/src/index.ts` re-exported `WebGPUDevice` as a **value**. A value re-export is a
+ * static edge, so every consumer of the barrel pulled in the device regardless.
+ *
+ * Measured on scenario 1 (one cube, no WebGPU): a **18,689-byte gzip chunk** on the critical path,
+ * `WebGPUDevice.ts` at 74,438 bytes raw.
+ *
+ * ## Why a new entry rather than dropping the export
+ *
+ * `WebGPUDevice` is a documented public export and WS-2.8 requires low-level escape hatches to stay
+ * reachable — a developer writing a custom WebGPU path must still be able to construct one. So it
+ * moves to `@aura3d/engine/rendering/webgpu`, and the barrel keeps only the **type**, which erases at
+ * build time. Nothing is removed from the public surface; one import specifier changes, recorded in
+ * `MIGRATION-1.6.md`.
+ */
+export { WebGPUDevice } from "./WebGPUDevice";
+export type { WebGPUAdapterLike, WebGPUBufferDescriptorLike, WebGPUBufferLike, WebGPUDeviceLike, WebGPUDeviceOptions, WebGPULike, WebGPUQueueLike, WebGPUSamplerDescriptorLike } from "./WebGPUDevice";
+//# sourceMappingURL=webgpu-device-entry.d.ts.map

package/dist/webgpu-device-entry.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"webgpu-device-entry.d.ts","sourceRoot":"","sources":["../../../../packages/rendering/src/webgpu-device-entry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,OAAO,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC;AAC9C,YAAY,EACV,iBAAiB,EACjB,0BAA0B,EAC1B,gBAAgB,EAChB,gBAAgB,EAChB,mBAAmB,EACnB,UAAU,EACV,eAAe,EACf,2BAA2B,EAC5B,MAAM,gBAAgB,CAAC"}

package/dist/webgpu-device-entry.js

@@ -0,0 +1,24 @@
+/**
+ * WS-2.2 — `WebGPUDevice` as its own entry point, so the barrel does not force it onto every bundle.
+ *
+ * ## The problem this solves
+ *
+ * `createRenderDevice` already loads the WebGPU device with `await import("./WebGPUDevice.js")`,
+ * deliberately, and says so: *"a statically imported branch is retained by bundlers even when the
+ * caller only ever asks for `webgl2`"*. That care was being undone one file away, because
+ * `packages/rendering/src/index.ts` re-exported `WebGPUDevice` as a **value**. A value re-export is a
+ * static edge, so every consumer of the barrel pulled in the device regardless.
+ *
+ * Measured on scenario 1 (one cube, no WebGPU): a **18,689-byte gzip chunk** on the critical path,
+ * `WebGPUDevice.ts` at 74,438 bytes raw.
+ *
+ * ## Why a new entry rather than dropping the export
+ *
+ * `WebGPUDevice` is a documented public export and WS-2.8 requires low-level escape hatches to stay
+ * reachable — a developer writing a custom WebGPU path must still be able to construct one. So it
+ * moves to `@aura3d/engine/rendering/webgpu`, and the barrel keeps only the **type**, which erases at
+ * build time. Nothing is removed from the public surface; one import specifier changes, recorded in
+ * `MIGRATION-1.6.md`.
+ */
+export { WebGPUDevice } from "./WebGPUDevice.js";
+//# sourceMappingURL=webgpu-device-entry.js.map

package/dist/webgpu-device-entry.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"webgpu-device-entry.js","sourceRoot":"","sources":["../../../../packages/rendering/src/webgpu-device-entry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,OAAO,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC"}

package/dist/webgpu.d.ts

@@ -0,0 +1,25 @@
+/**
+ * WS-2.2 — `WebGPUDevice` as its own entry point, so the barrel does not force it onto every bundle.
+ *
+ * ## The problem this solves
+ *
+ * `createRenderDevice` already loads the WebGPU device with `await import("./WebGPUDevice")`,
+ * deliberately, and says so: *"a statically imported branch is retained by bundlers even when the
+ * caller only ever asks for `webgl2`"*. That care was being undone one file away, because
+ * `packages/rendering/src/index.ts` re-exported `WebGPUDevice` as a **value**. A value re-export is a
+ * static edge, so every consumer of the barrel pulled in the device regardless.
+ *
+ * Measured on scenario 1 (one cube, no WebGPU): a **18,689-byte gzip chunk** on the critical path,
+ * `WebGPUDevice.ts` at 74,438 bytes raw.
+ *
+ * ## Why a new entry rather than dropping the export
+ *
+ * `WebGPUDevice` is a documented public export and WS-2.8 requires low-level escape hatches to stay
+ * reachable — a developer writing a custom WebGPU path must still be able to construct one. So it
+ * moves to `@aura3d/engine/rendering/webgpu`, and the barrel keeps only the **type**, which erases at
+ * build time. Nothing is removed from the public surface; one import specifier changes, recorded in
+ * `MIGRATION-1.6.md`.
+ */
+export { WebGPUDevice } from "./WebGPUDevice";
+export type { WebGPUAdapterLike, WebGPUBufferDescriptorLike, WebGPUBufferLike, WebGPUDeviceLike, WebGPUDeviceOptions, WebGPULike, WebGPUQueueLike, WebGPUSamplerDescriptorLike } from "./WebGPUDevice";
+//# sourceMappingURL=webgpu.d.ts.map

package/dist/webgpu.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"webgpu.d.ts","sourceRoot":"","sources":["../../../../packages/rendering/src/webgpu.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,OAAO,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC;AAC9C,YAAY,EACV,iBAAiB,EACjB,0BAA0B,EAC1B,gBAAgB,EAChB,gBAAgB,EAChB,mBAAmB,EACnB,UAAU,EACV,eAAe,EACf,2BAA2B,EAC5B,MAAM,gBAAgB,CAAC"}

package/dist/webgpu.js

@@ -0,0 +1,24 @@
+/**
+ * WS-2.2 — `WebGPUDevice` as its own entry point, so the barrel does not force it onto every bundle.
+ *
+ * ## The problem this solves
+ *
+ * `createRenderDevice` already loads the WebGPU device with `await import("./WebGPUDevice.js")`,
+ * deliberately, and says so: *"a statically imported branch is retained by bundlers even when the
+ * caller only ever asks for `webgl2`"*. That care was being undone one file away, because
+ * `packages/rendering/src/index.ts` re-exported `WebGPUDevice` as a **value**. A value re-export is a
+ * static edge, so every consumer of the barrel pulled in the device regardless.
+ *
+ * Measured on scenario 1 (one cube, no WebGPU): a **18,689-byte gzip chunk** on the critical path,
+ * `WebGPUDevice.ts` at 74,438 bytes raw.
+ *
+ * ## Why a new entry rather than dropping the export
+ *
+ * `WebGPUDevice` is a documented public export and WS-2.8 requires low-level escape hatches to stay
+ * reachable — a developer writing a custom WebGPU path must still be able to construct one. So it
+ * moves to `@aura3d/engine/rendering/webgpu`, and the barrel keeps only the **type**, which erases at
+ * build time. Nothing is removed from the public surface; one import specifier changes, recorded in
+ * `MIGRATION-1.6.md`.
+ */
+export { WebGPUDevice } from "./WebGPUDevice.js";
+//# sourceMappingURL=webgpu.js.map

package/dist/webgpu.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"webgpu.js","sourceRoot":"","sources":["../../../../packages/rendering/src/webgpu.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,OAAO,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC"}

package/package.json

@@ -1,18 +1,26 @@
 {
   "name": "@aura3d/rendering",
-  "version": "1.5.2",
+  "version": "2.0.0",
   "type": "module",
   "exports": {
     ".": {
       "types": "./dist/index.d.ts",
       "import": "./dist/index.js"
+    },
+    "./lean-runtime": {
+      "types": "./dist/lean-runtime.d.ts",
+      "import": "./dist/lean-runtime.js"
+    },
+    "./webgpu": {
+      "types": "./dist/webgpu.d.ts",
+      "import": "./dist/webgpu.js"
     }
   },
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "dependencies": {
-    "@aura3d/math": "1.5.2",
-    "@aura3d/scene": "1.5.2"
+    "@aura3d/math": "2.0.0",
+    "@aura3d/scene": "2.0.0"
   },
   "sideEffects": false,
   "description": "Render-device abstraction, WebGL2/mock backends, buffers, textures, shader modules, materials, render graphs, lighting, shadows, and particle rendering for Aura3D.",