@shivaedev/server 0.46.2 → 0.46.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +6 -0
- package/README.md +1 -1
- package/package.json +6 -6
package/CHANGELOG.md
CHANGED
package/README.md
CHANGED
|
@@ -149,7 +149,7 @@ A `defineService` declares its dependencies in `requires` and its operations yie
|
|
|
149
149
|
|
|
150
150
|
Pass `{ replacements: Layer.succeed(MyPort, implementation) }` as the second argument to `appModules`. Replacements take precedence over the combined default `ports` before module `services` acquire dependencies. Leave these ports unprovided in the module's service Layer; an adapter already captured by `Layer.provide` inside that Layer cannot be replaced from outside it. Missing ports and replacement Layer requirements remain in the host's requirement type. `workerHost` takes the same composition, provides its services to all module workers after database preparation, and scopes their lifetime to the returned Layer. Supply the shared `PgBoss` client through the service Layer in each process; the host and worker use the same module ports and replacements.
|
|
151
151
|
|
|
152
|
-
`workerHost` builds its database, services and workers inside the same redaction policy as `appHost`, and exports through the same OTLP pipeline, so do not provide `otlpTracing` around it. Once its workers are registered it logs `Worker ready to take jobs` inside that pipeline, so the application writes no readiness log of its own. Anything an application composes around the Layer that `workerHost` or `appHost` returns, such as `Layer.tap(() => Effect.logInfo(...))`, runs outside the host's redaction and exporter; put startup work in `services` or `workers` instead. Its logs, the causes its installed error reporters receive and its exported spans mask three sources: the built-in credential-shaped name rules from `@shivaedev/errors`, the names in `config.sensitiveKeys`, and the names of fields that the models of the repositories it builds mark sensitive with `sensitive: true` or a Redacted schema. A worker serves no RPC group, so no RPC schema adds names and no failure frame is masked. A job handler logs a stored row with that field as `<redacted>`, while what the job writes keeps the value. The jobs package
|
|
152
|
+
`workerHost` builds its database, services and workers inside the same redaction policy as `appHost`, and exports through the same OTLP pipeline, so do not provide `otlpTracing` around it. Once its workers are registered it logs `Worker ready to take jobs` inside that pipeline, so the application writes no readiness log of its own. Anything an application composes around the Layer that `workerHost` or `appHost` returns, such as `Layer.tap(() => Effect.logInfo(...))`, runs outside the host's redaction and exporter; put startup work in `services` or `workers` instead. Its logs, the causes its installed error reporters receive and its exported spans mask three sources: the built-in credential-shaped name rules from `@shivaedev/errors`, the names in `config.sensitiveKeys`, and the names of fields that the models of the repositories it builds mark sensitive with `sensitive: true` or a Redacted schema. A worker serves no RPC group, so no RPC schema adds names and no failure frame is masked. A job handler logs a stored row with that field as `<redacted>`, while what the job writes keeps the value. The jobs package logs each job attempt that fails or reaches its deadline at error level, with the failure as the line's cause, and the worker masks that line like its other logs. It reports nothing to the installed error reporters; a handler that wants a failure reported does so in its own Effect, as `Effect.withErrorReporting` does, and the worker masks the reported cause too.
|
|
153
153
|
|
|
154
154
|
```ts
|
|
155
155
|
workerHost({
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@shivaedev/server",
|
|
3
|
-
"version": "0.46.
|
|
3
|
+
"version": "0.46.3",
|
|
4
4
|
"description": "The Effect application host: HTTP and RPC serving, health, OTLP export, database and migrations, and development mode",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"effect"
|
|
@@ -59,12 +59,12 @@
|
|
|
59
59
|
"@effect/sql-pg": "4.1.4",
|
|
60
60
|
"@effect/vitest": "4.1.4",
|
|
61
61
|
"@shivaedev/access": "0.7.0",
|
|
62
|
-
"@shivaedev/admin": "0.29.
|
|
63
|
-
"@shivaedev/jobs": "0.
|
|
64
|
-
"@shivaedev/quality": "0.84.
|
|
62
|
+
"@shivaedev/admin": "0.29.9",
|
|
63
|
+
"@shivaedev/jobs": "0.45.0",
|
|
64
|
+
"@shivaedev/quality": "0.84.3",
|
|
65
65
|
"@shivaedev/rate-limit": "0.8.1",
|
|
66
66
|
"@shivaedev/service": "0.9.2",
|
|
67
|
-
"@shivaedev/test-kits": "0.16.
|
|
67
|
+
"@shivaedev/test-kits": "0.16.13",
|
|
68
68
|
"@shivaedev/test-sql": "0.26.1",
|
|
69
69
|
"@shivaedev/test-story": "0.52.6",
|
|
70
70
|
"@types/node": "24.19.2",
|
|
@@ -78,7 +78,7 @@
|
|
|
78
78
|
"@effect/platform-node": "4.1.4",
|
|
79
79
|
"@effect/sql-pg": "4.1.4",
|
|
80
80
|
"@effect/vitest": "4.1.4",
|
|
81
|
-
"@shivaedev/admin": "0.29.
|
|
81
|
+
"@shivaedev/admin": "0.29.9",
|
|
82
82
|
"better-auth": "1.7.23",
|
|
83
83
|
"effect": "4.1.4"
|
|
84
84
|
},
|