three-slicer-viewer 0.2.5 → 0.3.0

package/COMPONENTS.md

@@ -1,4 +1,7 @@
-# three-slicer/components
+# three-slicer-viewer/components — the settings form
+
+(Published as `three-slicer-viewer/components`, MIT. `three-slicer/components` is the same component with upstream's
+schema, tab tree and toggle rules plugged in; everything below applies to both.)
 
 Reusable React components for the browser slicer. Props-driven — no global state, no React context, no router coupling (proven standalone by the tarball consumer gate `packages/pack_check.sh`).
 

package/README.md

@@ -9,6 +9,10 @@ exports; it does not slice. Slicing is plugged in through two props — `slicer`
 `catalog` (vendor presets) — which `three-slicer/viewer` supplies. Install `three-slicer` for that, and note that
 doing so puts your application under AGPL.
 
+Developed in the [`Web_Three_Slicer`](https://github.com/kimgh06/Web_Three_Slicer) monorepo (`packages-mit/`), where it
+is built and tested beside the kernel; this repository is that folder's history, pushed on every release. Issues and
+pull requests are welcome here — a change lands upstream and comes back with the next sync.
+
 ## The viewer
 
 ```jsx

package/VIEWER.md

@@ -1,4 +1,7 @@
-# three-slicer/viewer
+# three-slicer-viewer — the viewer
+
+(Published as `three-slicer-viewer`, MIT. `three-slicer/viewer` is the same component with the WASM kernel and the
+vendor catalog plugged in; everything below applies to both.)
 
 3D slicer viewer as a React component: three.js viewport (orbit/transform gizmos), model import (STL/OBJ/3MF/AMF/PLY + pluggable formats such as STEP, multi-object, drag & drop), Web Worker slicing via `three-slicer`, support and material painting, per-extruder filament presets, multi-plate, and a GPU-instanced volumetric toolpath preview ported from OrcaSlicer's libvgcode (millions of segments in a single draw path, per-feature colors, layer range slider, G-code export).
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "three-slicer-viewer",
-  "version": "0.2.5",
-  "description": "The three-slicer viewer without the slicer \u2014 model loading, G-code parsing, GPU toolpath rendering and the settings transforms, under MIT. Plug a slicer in through the `slicer` prop.",
+  "version": "0.3.0",
+  "description": "The three-slicer viewer without the slicer — model loading, G-code parsing, GPU toolpath rendering and the settings transforms, under MIT. Plug a slicer in through the `slicer` prop.",
   "license": "MIT",
   "type": "module",
   "sideEffects": false,
@@ -76,8 +76,15 @@
       "optional": true
     }
   },
+  "devDependencies": {
+    "react": "^18.3.1",
+    "react-dom": "^18.3.1",
+    "three": "^0.160.0",
+    "vite": "^5.4.11"
+  },
   "scripts": {
     "build": "vite build && cp src/make_worker.js dist/make_worker.js",
-    "prepublishOnly": "npm run build && node test_version_lockstep.mjs && node test_toolpath_contract.mjs"
+    "prepublishOnly": "npm run build && node test_version_lockstep.mjs && node test_toolpath_contract.mjs",
+    "test": "for f in test_*.mjs; do node $f || exit 1; done"
   }
 }

package/types/loaders.d.ts

@@ -1,4 +1,4 @@
-// three-slicer/viewer/loaders — pure loaders, independent of the kernel.
+// three-slicer-viewer/loaders — pure loaders, independent of the kernel.
 
 /** The 5 built-ins plus any extension registered via `registerLoader()`, which pushes onto this array. */
 export const SUPPORTED_EXT: string[]
@@ -20,7 +20,7 @@ export function loadModel(name: string, buffer: ArrayBuffer): Promise<LoadedObje
  * so the app wires them up itself. The `<Viewport/>` file dialog and drag-and-drop filters pick them up automatically.
  *
  * ```js
- * import { registerLoader } from 'three-slicer/viewer/loaders'
+ * import { registerLoader } from 'three-slicer-viewer/loaders'
  * registerLoader('step,stp', async (buffer, name) => [{ name, modelPos }])
  * ```
  */