sveltekit-discriminated-fields 0.1.0 → 0.1.2

package/README.md

@@ -1,10 +1,10 @@
 # sveltekit-discriminated-fields
 
-Type-safe discriminated union support for SvelteKit form fields.
+Type-safe discriminated union support for SvelteKit remote function form fields.
 
 ## The Problem
 
-When using SvelteKit's `form()` with discriminated union schemas (e.g., Zod's `z.discriminatedUnion`), the generated `fields` object is a **union of field objects**. TypeScript only allows access to properties that exist on ALL variants - meaning variant-specific fields are completely inaccessible.
+When using SvelteKit's remote function `form()` with discriminated union schemas (e.g., Zod's `z.discriminatedUnion`), the generated `fields` object is a **union of field objects**. TypeScript only allows access to properties that exist on ALL variants - meaning variant-specific fields are completely inaccessible.
 
 Given a typical SvelteKit setup:
 
@@ -167,6 +167,10 @@ type Payment = DiscriminatedData<typeof payment>;
 
 Useful when you need to reference the data type elsewhere, such as defining default values or passing data to other functions.
 
+## Note on Runtime Behavior
+
+Type narrowing is compile-time only. At runtime, `'width' in shape` will return `true` even when `kindValue === 'circle'`, because all variant fields exist on the underlying object.
+
 ## License
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "sveltekit-discriminated-fields",
-	"version": "0.1.0",
+	"version": "0.1.2",
 	"description": "Type-safe discriminated union support for SvelteKit form fields",
 	"type": "module",
 	"exports": {
@@ -16,7 +16,8 @@
 		"build": "tsc -p tsconfig.build.json",
 		"check": "tsc --noEmit",
 		"test:types": "tsc -p test/types/tsconfig.json",
-		"test": "npm run test:types",
+		"test:runtime": "npm run build && tsc -p test/runtime/tsconfig.json && npx tsx test/runtime/has.test.ts",
+		"test": "npm run test:types && npm run test:runtime",
 		"prepublishOnly": "npm run test && npm run build"
 	},
 	"keywords": [