@effected/app 0.18.0 → 0.19.1

package/App.js

@@ -73,9 +73,13 @@ var App = class {
 	*
 	* The documented limit: code paths that actually exercise `ensure*` **die**
 	* against `FileSystem.layerNoop` — it is a stub, not a working filesystem.
-	* `layerTest` is for testing logic that *uses* the control plane; a test of
-	* real directory behaviour uses {@link App.layer} with a temp-directory
-	* `HOME`.
+	* `layerTest` is for testing logic that *uses* the control plane. A test of
+	* real directory behaviour composes `AppDirs.layer` over `@effected/memfs`,
+	* whose `ensure*` members then create directories on an in-memory volume.
+	* The databases are the exception: `Store` and `Cache` open their SQLite
+	* files through the native binding, which never sees the `FileSystem`
+	* service, so a test of {@link App.layer} end to end still needs a
+	* temp-directory `HOME`.
 	*/
 	static layerTest = layerTest;
 };

package/README.md

@@ -144,7 +144,7 @@ Two properties to be deliberate about. **A resolver that finds nothing falls thr
 
 ### Wiring the flag to the layer
 
-A layer is built before a CLI parses anything, so the parsed `--config` has to reach `AppConfig.layer` somehow. `effect/unstable/cli` has two ways, and neither needs an `Effect.provide` inside the handler.
+A layer is built before a CLI parses anything, so the parsed `--config` has to reach `AppConfig.layer` somehow. `effect/cli` has two ways, and neither needs an `Effect.provide` inside the handler.
 
 For a single command, `Command.provide` takes **a function of the parsed input**, not just a finished layer:
 

package/index.d.ts

@@ -182,9 +182,13 @@ export declare class App {
    *
    * The documented limit: code paths that actually exercise `ensure*` **die**
    * against `FileSystem.layerNoop` — it is a stub, not a working filesystem.
-   * `layerTest` is for testing logic that *uses* the control plane; a test of
-   * real directory behaviour uses {@link App.layer} with a temp-directory
-   * `HOME`.
+   * `layerTest` is for testing logic that *uses* the control plane. A test of
+   * real directory behaviour composes `AppDirs.layer` over `@effected/memfs`,
+   * whose `ensure*` members then create directories on an in-memory volume.
+   * The databases are the exception: `Store` and `Cache` open their SQLite
+   * files through the native binding, which never sees the `FileSystem`
+   * service, so a test of {@link App.layer} end to end still needs a
+   * temp-directory `HOME`.
    */
   static readonly layerTest: (options: AppTestOptions) => Layer.Layer<Xdg | AppDirs | Store | Cache, AppError>;
 }
@@ -264,7 +268,7 @@ interface AppConfigOptions<A, I, RR = never> {
    * unchanged: `XdgConfig.resolver`, then `XdgConfig.nativeResolver`.
    *
    * A layer is built before a CLI parses anything, so getting the parsed flag
-   * here is the one wiring question this option raises. `effect/unstable/cli`
+   * here is the one wiring question this option raises. `effect/cli`
    * answers it twice, and neither answer needs an `Effect.provide` inside the
    * handler: `Command.provide` accepts a **function of the parsed input**, and
    * for several subcommands sharing one flag, `GlobalFlag.setting` makes the

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/app",
-	"version": "0.18.0",
+	"version": "0.19.1",
 	"private": false,
 	"description": "The application control plane for Effect: one layer wiring XDG-namespaced directories, a migrated SQLite store, a TTL cache and a config file to the same place.",
 	"keywords": [
@@ -39,10 +39,10 @@
 		"./package.json": "./package.json"
 	},
 	"peerDependencies": {
-		"@effected/config-file": "^0.12.0",
-		"@effected/store": "^0.10.0",
-		"@effected/xdg": "^0.7.0",
-		"effect": "4.0.0-rc.117"
+		"@effected/config-file": "^0.13.1",
+		"@effected/store": "^0.11.0",
+		"@effected/xdg": "^0.8.2",
+		"effect": "4.0.0-rc.118"
 	},
 	"engines": {
 		"node": ">=24.11.0"