@rc312/tss-effect-serverfn 0.1.0 → 0.2.0

package/README.md

@@ -7,7 +7,7 @@ Write TanStack Start server functions with **Effect Schemas and Effect handlers*
 In an existing **TanStack React Start** app using **Effect 4**:
 
 ```sh
-bun add @rc312/tss-effect-serverfn 'effect@^4.0.5'
+bun add @rc312/tss-effect-serverfn 'effect@^4.1.2'
 ```
 
 ### 1. Register the Vite plugin
@@ -120,8 +120,8 @@ The three environment helpers return lazy Effects for composition. Use `yield*`
 ## More
 
 - [Composition examples: pipe, flow, Effect.fn, and combinators](docs/composition.md)
-- [Runnable basic and service examples](https://github.com/RyanCallahan312/tss-effect-serverfn/tree/main/examples)
+- [Runnable basic and service examples](examples)
 - [Application services, errors, reporting, and execution details](docs/usage.md)
-- [Workspace development](https://github.com/RyanCallahan312/tss-effect-serverfn#development)
+- [Workspace development](docs/development.md)
 
-Tested with Effect 4.0.5, React Start 1.169.2, and Vite 8.3.4. Supported peer ranges are in `package.json`.
+Tested with Effect 4.1.2, React Start 1.169.2, and Vite 8.3.4. Supported peer ranges are in `package.json`.

package/docs/composition.md

@@ -2,7 +2,7 @@
 
 Handlers can return any native Effect. `Effect.gen`, `pipe`, `.pipe`, `flow`, `Effect.fn`, and do notation all use the same configured runtime, decoded input, and request Scope.
 
-Start with the [configured factory](../README.md#quick-start). Try the examples in the [basic app](https://github.com/RyanCallahan312/tss-effect-serverfn/tree/main/examples/basic): its **Composition** selector runs five equivalent server functions through real RPCs.
+Start with the [configured factory](../README.md#quick-start). Try the examples in the [basic app](../examples/basic): its **Composition** selector runs five equivalent server functions through real RPCs.
 
 ## Choose a composition style
 
@@ -136,7 +136,7 @@ Each step retains earlier fields. A later `bind` or `let` callback can use those
 
 ## Pipe service work and recover a business error
 
-The [services app](https://github.com/RyanCallahan312/tss-effect-serverfn/tree/main/examples/services) provides `Notes` through its application-owned `ManagedRuntime`. Its `notes.functions.ts` composes the service directly:
+The [services app](../examples/services) provides `Notes` through its application-owned `ManagedRuntime`. Its `notes.functions.ts` composes the service directly:
 
 ```ts
 import { Effect, flow, Schema } from "effect";

package/docs/development.md

@@ -0,0 +1,48 @@
+# Package development
+
+Run the following commands from the repository root unless noted otherwise.
+
+## Development
+
+Use Bun 1.3.13 and Node.js 22.19 or newer.
+
+```sh
+bun install
+bun run check       # lint, builds, typechecks, and package tests
+bun run build       # package and example builds through Turbo
+bun run dev         # package watcher and both example dev servers
+bun run format     # apply formatting and safe lint fixes
+```
+
+The package builds with standard `tsc -b`. Effect and TanStack are peers so applications share the same runtime and framework instances.
+
+## Browser tests
+
+```sh
+(cd packages/tss-effect-serverfn && bunx --no-install playwright install chromium)
+bun run test:e2e
+```
+
+The suite runs both examples against Vite dev and production preview, using real browser interactions and RPC responses. See [E2E coverage and debugging](../e2e/README.md). Failures retain Playwright traces and screenshots in the package directory.
+
+## TypeScript configuration
+
+`tsconfig.base.json` holds shared strict compiler settings and Effect diagnostics. Each package extends it with its own source include. The root `tsconfig.json` is a solution config: add a project reference there when adding a package, and add package-level references for workspace dependencies.
+
+`bunx tsc -b` builds the package solution. Examples use Vite-oriented TypeScript configs and `noEmit`. `bun run typecheck` builds first so generated route types and package exports exist, then checks the package, both apps, and E2E code. Package builds emit JavaScript, declarations, and maps into `dist/`; the published package includes `src/` so map navigation works.
+
+## Releases
+
+The package is published as `@rc312/tss-effect-serverfn` under the MIT license. Nothing is published automatically on push.
+
+1. Run `bun run changeset` and commit the generated changeset with your changes.
+2. Run `bun run version-packages`, then `bun install` to refresh the lockfile. Commit the version changes, changelog, and lockfile to `main`.
+3. Inspect the artifact locally:
+
+   ```sh
+   bun run check
+   cd packages/tss-effect-serverfn
+   npm pack --dry-run
+   ```
+
+4. To publish locally, authenticate with `npm login`, return to the root, and run `bun run release`. Changesets publishes only unreleased package versions. Push any generated version tags if you want them recorded on GitHub.

package/docs/usage.md

@@ -204,7 +204,7 @@ Optional fields returned by `resolve`:
 | `reportFailure(report)` | Effect-valued replacement for the default reporting action |
 | `reportTimeout` | Native `Duration.Input`; defaults to `"5 seconds"` for the override |
 
-An override is awaited after request-scope cleanup, with application services and request metadata. Its faults/timeouts cannot replace the business rejection. Use `Effect.tryPromise` and its signal for foreign reporters. Compose `ErrorReporter.report` explicitly if the override should also invoke native reporters. ErrorReporter and the HTTP request APIs are unstable in Effect 4.0.5.
+An override is awaited after request-scope cleanup, with application services and request metadata. Its faults/timeouts cannot replace the business rejection. Use `Effect.tryPromise` and its signal for foreign reporters. Compose `ErrorReporter.report` explicitly if the override should also invoke native reporters. ErrorReporter and the HTTP request APIs are unstable in Effect 4.1.2.
 
 For outer framework reporting, `@rc312/tss-effect-serverfn/server` exports:
 

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "@rc312/tss-effect-serverfn",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Typed Effect execution and safe failure boundaries for TanStack Start server functions.",
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/RyanCallahan312/tss-effect-serverfn.git",
+    "url": "git+https://github.com/RyanCallahan312/effect-extensions.git",
     "directory": "packages/tss-effect-serverfn"
   },
   "files": [
@@ -32,9 +32,10 @@
   "scripts": {
     "build": "tsc -b tsconfig.json",
     "dev": "tsc -b tsconfig.json --watch",
-    "typecheck": "tsc --noEmit -p tsconfig.json --tsBuildInfoFile .cache/typecheck.tsbuildinfo && tsc -p tsconfig.test.json && tsc -p tsconfig.fixtures.json",
+    "typecheck": "tsc --noEmit -p tsconfig.json --tsBuildInfoFile .cache/typecheck.tsbuildinfo && tsc -p tsconfig.test.json && tsc -p tsconfig.fixtures.json && tsc -p e2e/tsconfig.json",
     "test": "vitest run && node --test test/*.test.mjs",
-    "prepack": "bun run build"
+    "prepack": "bun run build",
+    "test:e2e": "playwright test"
   },
   "dependencies": {
     "@babel/core": "^7.29.7",
@@ -42,7 +43,8 @@
     "@standard-schema/spec": "^1.1.0"
   },
   "devDependencies": {
-    "@effect/vitest": "^4.0.5",
+    "@effect/vitest": "^4.1.2",
+    "@playwright/test": "^1.64.1",
     "@tanstack/react-router": "1.170.44",
     "@tanstack/start-storage-context": "^1.167.39",
     "@types/babel__core": "^7.20.5",
@@ -55,7 +57,7 @@
   "peerDependencies": {
     "@tanstack/react-start": "^1.169.2",
     "@tanstack/router-core": "^1.171.37",
-    "effect": "^4.0.5",
+    "effect": "^4.1.2",
     "vite": "^8.3.4"
   },
   "peerDependenciesMeta": {
@@ -64,6 +66,6 @@
     }
   },
   "engines": {
-    "node": ">=22.12.0"
+    "node": ">=22.19.0"
   }
 }