@selvajs/solve 1.0.0-beta.8 → 1.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@selvajs/solve",
-  "version": "1.0.0-beta.8",
+  "version": "1.0.0",
   "description": "One owner for the Selva solve flow — input change to solve result, on both sides of the wire, with no transport and no UI",
   "author": "VektorNode",
   "license": "MIT",
@@ -55,13 +55,16 @@
   },
   "files": [
     "dist",
-    "README.md"
+    "README.md",
+    "!**/__tests__/**",
+    "!**/*.test.*",
+    "!**/*.spec.*"
   ],
   "sideEffects": false,
   "dependencies": {
-    "@selvajs/compute": "^4.0.0-beta.4",
-    "@selvajs/platform": "^0.16.1-beta.1",
-    "@selvajs/schemas": "5.0.0-beta.1"
+    "@selvajs/compute": "^4.0.0",
+    "@selvajs/platform": "^0.17.0",
+    "@selvajs/schemas": "5.0.0"
   },
   "devDependencies": {
     "@eslint/js": "^10.0.1",
@@ -71,21 +74,21 @@
     "eslint-config-prettier": "^10.1.8",
     "globals": "^17.5.0",
     "prettier": "^3.9.6",
-    "tsup": "^8.5.1",
+    "tsdown": "^0.22.14",
     "typescript": "~6.0.3",
-    "vite": "^8.1.5",
-    "vitest": "^4.1.10"
+    "vite": "^8.2.1",
+    "vitest": "^4.1.10",
+    "@selvajs/config": "0.0.4"
   },
   "engines": {
-    "node": ">=22.0.0"
+    "node": ">=24.0.0"
   },
   "publishConfig": {
     "access": "public"
   },
   "scripts": {
-    "build": "pnpm type-check && pnpm clean && tsup",
-    "dev": "tsup --watch",
-    "clean": "node --input-type=module -e \"import fs from 'fs'; fs.rmSync('dist', { recursive: true, force: true })\"",
+    "build": "pnpm type-check && tsdown",
+    "dev": "tsdown --watch",
     "lint": "eslint .",
     "lint:fix": "eslint . --fix",
     "format": "prettier --write .",

package/dist/shared.cjs.map

@@ -1 +0,0 @@
-{"version":3,"sources":["/home/runner/work/selva/selva/packages/solve/dist/shared.cjs"],"names":[],"mappings":"AAAA","file":"/home/runner/work/selva/selva/packages/solve/dist/shared.cjs"}

package/dist/shared.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":[],"sourcesContent":[],"mappings":"","names":[]}

package/dist/solve-fn-DrRgaPZ5.d.cts

@@ -1,46 +0,0 @@
-/**
- * The solve contract — what a solve returns and what a caller supplies to run one.
- *
- * Lives in `shared/` because both halves of the package speak it: `client/` calls a `SolveFn` and
- * stores its `SolveResult`; `server/` produces the payload one is built from.
- */
-/**
- * `TMesh` is deliberately opaque and defaults to `unknown`: this package never inspects meshes, and
- * typing them would drag a renderer dependency into a package whose whole point is not having one.
- * The app that owns assembly (parse → `THREE.Object3D[]`) is the only place that knows the concrete
- * type, and it narrows by writing `SolveResult<THREE.Object3D>` at its own seam.
- */
-interface SolveResult<TMesh = unknown, TSource = unknown> {
-    outputs: Record<string, unknown>;
-    meshes?: TMesh[];
-    errors?: string[];
-    warnings?: string[];
-    /**
-     * The unparsed payload this result was built from, passed through verbatim. Opaque here for the
-     * same reason as `TMesh`: a consumer that must persist or re-submit exactly what it showed the
-     * user narrows it at its own seam. Travels with the result through the driver's memo, so a
-     * cached hit carries the source that produced it. Unlike `meshes` it needs no ownership policy —
-     * it is inert data, not a GPU-backed handle.
-     *
-     * Supplied by the `SolveFn`, so it is present only when the one in use sets it
-     * (`createComputeFetchSolveFn` does). A transport with no raw payload to hand back leaves it
-     * absent — see `values` on telling absent from unsupported.
-     */
-    source?: TSource;
-    /**
-     * The input set that produced this result, stamped by the driver rather than the `SolveFn` — a
-     * memo hit never calls the `SolveFn`, so a consumer reading values captured inside it would pair
-     * the on-screen result with whatever solved last. Keeping the pair atomic is the point: a commit
-     * path holding a `SolveResult` cannot mismatch artifact and inputs.
-     *
-     * Present only from a driver that owns a request/response pair (`createRequestResponseDriver`).
-     * A push driver cannot attribute an incoming frame to a request and must leave this absent
-     * rather than guess — so `undefined` means "this transport does not supply it", not "no solve
-     * yet", and a consumer that needs the pair requires a request/response driver. See `SolveDriver`.
-     */
-    values?: Record<string, unknown>;
-}
-/** Implementations should listen to `signal` and abort/clean up when it fires. */
-type SolveFn<TMesh = unknown, TSource = unknown> = (values: Record<string, unknown>, signal: AbortSignal) => Promise<SolveResult<TMesh, TSource>>;
-
-export type { SolveFn as S, SolveResult as a };

package/dist/solve-fn-DrRgaPZ5.d.ts

@@ -1,46 +0,0 @@
-/**
- * The solve contract — what a solve returns and what a caller supplies to run one.
- *
- * Lives in `shared/` because both halves of the package speak it: `client/` calls a `SolveFn` and
- * stores its `SolveResult`; `server/` produces the payload one is built from.
- */
-/**
- * `TMesh` is deliberately opaque and defaults to `unknown`: this package never inspects meshes, and
- * typing them would drag a renderer dependency into a package whose whole point is not having one.
- * The app that owns assembly (parse → `THREE.Object3D[]`) is the only place that knows the concrete
- * type, and it narrows by writing `SolveResult<THREE.Object3D>` at its own seam.
- */
-interface SolveResult<TMesh = unknown, TSource = unknown> {
-    outputs: Record<string, unknown>;
-    meshes?: TMesh[];
-    errors?: string[];
-    warnings?: string[];
-    /**
-     * The unparsed payload this result was built from, passed through verbatim. Opaque here for the
-     * same reason as `TMesh`: a consumer that must persist or re-submit exactly what it showed the
-     * user narrows it at its own seam. Travels with the result through the driver's memo, so a
-     * cached hit carries the source that produced it. Unlike `meshes` it needs no ownership policy —
-     * it is inert data, not a GPU-backed handle.
-     *
-     * Supplied by the `SolveFn`, so it is present only when the one in use sets it
-     * (`createComputeFetchSolveFn` does). A transport with no raw payload to hand back leaves it
-     * absent — see `values` on telling absent from unsupported.
-     */
-    source?: TSource;
-    /**
-     * The input set that produced this result, stamped by the driver rather than the `SolveFn` — a
-     * memo hit never calls the `SolveFn`, so a consumer reading values captured inside it would pair
-     * the on-screen result with whatever solved last. Keeping the pair atomic is the point: a commit
-     * path holding a `SolveResult` cannot mismatch artifact and inputs.
-     *
-     * Present only from a driver that owns a request/response pair (`createRequestResponseDriver`).
-     * A push driver cannot attribute an incoming frame to a request and must leave this absent
-     * rather than guess — so `undefined` means "this transport does not supply it", not "no solve
-     * yet", and a consumer that needs the pair requires a request/response driver. See `SolveDriver`.
-     */
-    values?: Record<string, unknown>;
-}
-/** Implementations should listen to `signal` and abort/clean up when it fires. */
-type SolveFn<TMesh = unknown, TSource = unknown> = (values: Record<string, unknown>, signal: AbortSignal) => Promise<SolveResult<TMesh, TSource>>;
-
-export type { SolveFn as S, SolveResult as a };