dropsh 0.7.1 → 0.7.3

package/README.md

@@ -235,10 +235,14 @@ environment variable:
 | 2 | `--connection <id>` | names an **entry** |
 | 3 | `$DROPSH_CONFIG` | names a **file** |
 | 4 | `$DROPSH_CONNECTION` | names an **entry** |
-| 5 | `./dropsh.config.js` | the cwd default |
+| 5 | existing default config | `./dropsh.config.js` by default |
+| 6 | sole named connection | only when the default is absent |
+| 7 | default config path | lets loading report the missing config |
 
 `--config` and `--connection` given together is not an error: `--config` names a
-file and wins.
+file and wins. When no selector is set and the default config does not exist,
+exactly one `.js` file in the connections directory is selected automatically.
+Two or more named connections remain ambiguous and require a selector.
 
 An unknown id is a hard error — non-zero exit, naming the id, the directory
 searched and the available ids. Nothing is prompted and nothing is created, so
@@ -680,6 +684,10 @@ const config = resolveConfigSource({
 // config.path and config.source identify the selected config file and selector.
 ```
 
+Embedders whose default config is not `./dropsh.config.js` can pass its path as
+`defaultConfig`. An existing default wins over implicit sole-connection
+selection; when it is absent, a sole named connection is selected instead.
+
 The same entry point also exports `CWD_CONFIG_FILE`, `listConnectionIds`, and
 `listConnections`, plus the `ConfigSource`, `ConfigSourceKind`,
 `ConnectionEntry`, `ResolveConfigSourceInput`, and `ResolveConnectionsDirInput`

package/dist/src/core/connections.d.ts

@@ -1,7 +1,7 @@
 /** The name of the config file dropsh falls back to in the current directory. */
 export declare const CWD_CONFIG_FILE = "dropsh.config.js";
 /** Which selector produced the resolved config path. */
-export type ConfigSourceKind = "flag-config" | "flag-connection" | "env-config" | "env-connection" | "cwd";
+export type ConfigSourceKind = "flag-config" | "flag-connection" | "env-config" | "env-connection" | "default-config" | "sole-connection" | "cwd";
 /** The chosen config file plus the provenance of that choice. */
 export interface ConfigSource {
     path: string;
@@ -25,6 +25,8 @@ export interface ResolveConfigSourceInput {
     config?: string | undefined;
     /** `--connection <id>`. */
     connection?: string | undefined;
+    /** Embedder-owned default config, used ahead of an implicit sole connection. */
+    defaultConfig?: string | undefined;
     connectionsDir?: string;
     env?: NodeJS.ProcessEnv;
     cwd?: string;
@@ -32,8 +34,10 @@ export interface ResolveConfigSourceInput {
 /**
  * Resolve the config file for this invocation, highest selector first:
  * `--config` > `--connection` > `$DROPSH_CONFIG` > `$DROPSH_CONNECTION` >
- * `./dropsh.config.js`. `--config` and `--connection` together is not an error:
- * `--config` names a *file* and that is its stated meaning, so it wins silently.
+ * an existing default config > the sole named connection > the default path.
+ * The default path is `./dropsh.config.js`. `--config` and `--connection`
+ * together is not an error: `--config` names a *file* and that is its stated
+ * meaning, so it wins silently.
  *
  * Returns the path *and* its provenance, so every caller — the command context,
  * the auth wiring, the pre-parse plugin bootstrap and `connections list` — reads

package/dist/src/core/connections.js

@@ -26,8 +26,8 @@ function toIds(entries) {
 }
 /**
  * Sorted ids of the `.js` files in `dir`; `[]` when the directory is absent.
- * Synchronous because it is only reached on the unknown-id error path, and the
- * resolver itself has to stay synchronous for the commander option wiring.
+ * Synchronous because the resolver uses it for implicit sole-connection
+ * selection and has to stay synchronous for the commander option wiring.
  */
 function listConnectionIdsSync(dir) {
     try {
@@ -40,8 +40,10 @@ function listConnectionIdsSync(dir) {
 /**
  * Resolve the config file for this invocation, highest selector first:
  * `--config` > `--connection` > `$DROPSH_CONFIG` > `$DROPSH_CONNECTION` >
- * `./dropsh.config.js`. `--config` and `--connection` together is not an error:
- * `--config` names a *file* and that is its stated meaning, so it wins silently.
+ * an existing default config > the sole named connection > the default path.
+ * The default path is `./dropsh.config.js`. `--config` and `--connection`
+ * together is not an error: `--config` names a *file* and that is its stated
+ * meaning, so it wins silently.
  *
  * Returns the path *and* its provenance, so every caller — the command context,
  * the auth wiring, the pre-parse plugin bootstrap and `connections list` — reads
@@ -66,7 +68,17 @@ export function resolveConfigSource(input = {}) {
         const id = env.DROPSH_CONNECTION;
         return { path: requireConnection(dir, id), source: "env-connection", id };
     }
-    return { path: join(cwd, CWD_CONFIG_FILE), source: "cwd" };
+    const defaultConfig = input.defaultConfig ?? join(cwd, CWD_CONFIG_FILE);
+    const defaultSource = input.defaultConfig === undefined ? "cwd" : "default-config";
+    if (existsSync(defaultConfig))
+        return { path: defaultConfig, source: defaultSource };
+    const available = listConnectionIdsSync(dir);
+    if (available.length === 1) {
+        const id = available[0];
+        if (id)
+            return { path: connectionPath(dir, id), source: "sole-connection", id };
+    }
+    return { path: defaultConfig, source: defaultSource };
 }
 /**
  * The path of connection `id`, or a `ConfigError` naming the id, the directory

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dropsh",
-  "version": "0.7.1",
+  "version": "0.7.3",
   "description": "Entity-agnostic helper CLI for Drupal 11 JSON:API, used by the dropsh Claude skill for editorial publishing workflows.",
   "type": "module",
   "bin": {