dirsql 0.4.6 → 0.4.8

package/dist/cli/resolve-config-extensions.d.ts

@@ -1,5 +1,5 @@
 /**
- * Return `argv` augmented with `--extension <path>[::entrypoint]` flags when the
+ * Return `argv` augmented with `--extension <path>[::entrypoint]` flags when a
  * TOML config names an extension by package name; otherwise return `argv`
  * unchanged. Throws if a package name cannot be resolved (surfaced by the
  * launcher as a clean error).

package/dist/cli/resolve-config-extensions.js

@@ -1,11 +1,14 @@
-// Launcher-side resolution of a TOML config's `[[dirsql.extension]]` entries.
+// Launcher-side resolution of the TOML configs' `[[dirsql.extension]]` entries.
 //
 // The compiled `dirsql` binary loads config extensions literally — it has no
-// `require.resolve`, so it cannot resolve a bare **package name**. When a
-// TOML config names an extension by package name, the shared SDK resolver
-// resolves every entry and this launcher passes the resolved literal paths
-// to the binary via repeatable `--extension` flags; the binary then loads
-// those and ignores the config's own extension entries.
+// `require.resolve`, so it cannot resolve a bare **package name**. When any
+// TOML config in argv names an extension by package name, the shared SDK
+// resolver resolves every config's entries and this launcher passes the
+// resolved literal paths to the binary via repeatable `--extension` flags;
+// the binary then loads those and ignores the configs' own extension entries.
+//
+// The `-c`/`--config` flag is repeatable, so the scan collects every
+// occurrence, in argv order.
 //
 // Native-language configs (`.py`/`.js`/`.mjs`/`.cjs`) are untouched: the binary
 // dispatches those to `dirsql interpret`, whose handshake already carries
@@ -14,21 +17,37 @@ import { existsSync } from "node:fs";
 // Config extensions the binary dispatches to `dirsql interpret`; never
 // pre-resolved here (that path resolves via the handshake).
 const NATIVE_CONFIG_SUFFIXES = [".py", ".js", ".mjs", ".cjs"];
-/** The `--config` value from argv (`--config X` or `--config=X`), or the default. */
-function configPathFromArgv(argv) {
-    for (let i = 0; i < argv.length; i++) {
-        const a = argv[i];
-        if (a === "--config") {
-            return argv[i + 1] ?? "";
+/**
+ * Every config value in argv, in order (`--config X`, `--config=X`, `-c X`,
+ * `-c=X`, `-cX`), or the default when none are given.
+ */
+function configPathsFromArgv(argv) {
+    const paths = [];
+    let expectValue = false;
+    for (const a of argv) {
+        if (expectValue) {
+            paths.push(a);
+            expectValue = false;
+        }
+        else if (a === "--config" || a === "-c") {
+            expectValue = true;
         }
-        if (a?.startsWith("--config=")) {
-            return a.slice("--config=".length);
+        else if (a.startsWith("--config=")) {
+            paths.push(a.slice("--config=".length));
         }
+        else if (a.startsWith("-c")) {
+            const value = a.slice("-c".length);
+            paths.push(value.startsWith("=") ? value.slice("=".length) : value);
+        }
+    }
+    if (expectValue) {
+        // A bare trailing flag (no following value) yields "".
+        paths.push("");
     }
-    return "./.dirsql.toml";
+    return paths.length > 0 ? paths : ["./.dirsql.toml"];
 }
 /**
- * Return `argv` augmented with `--extension <path>[::entrypoint]` flags when the
+ * Return `argv` augmented with `--extension <path>[::entrypoint]` flags when a
  * TOML config names an extension by package name; otherwise return `argv`
  * unchanged. Throws if a package name cannot be resolved (surfaced by the
  * launcher as a clean error).
@@ -37,18 +56,16 @@ export async function withResolvedExtensions(argv) {
     if (argv[0] === "init") {
         return argv;
     }
-    const configPath = configPathFromArgv(argv);
-    if (NATIVE_CONFIG_SUFFIXES.some((s) => configPath.endsWith(s))) {
-        return argv;
-    }
+    const configPaths = configPathsFromArgv(argv).filter((p) => !NATIVE_CONFIG_SUFFIXES.some((s) => p.endsWith(s)));
     // The shared resolver pulls in smol-toml, which only a TOML config on disk
     // can need. Guarding on the same `existsSync` the resolver itself starts
-    // with keeps the parser off the common launch path entirely (#720).
-    if (!existsSync(configPath)) {
+    // with keeps the parser off the common launch path entirely (#720); the
+    // resolver skips any individually-missing config on its own.
+    if (!configPaths.some((p) => existsSync(p))) {
         return argv;
     }
-    const { resolveConfigExtensionSpecs } = await import("../resolve-config-extensions.js");
-    const specs = resolveConfigExtensionSpecs(configPath);
+    const { resolveConfigsExtensionSpecs } = await import("../resolve-config-extensions.js");
+    const specs = resolveConfigsExtensionSpecs(configPaths);
     if (specs === null) {
         return argv;
     }

package/docs/reference/cli.md

@@ -69,6 +69,7 @@ Config flags are subcommand-local: pass them after `server`
 | `--host <addr>` | `localhost` | Bind address. |
 | `--port <n>` | `7117` | TCP port to bind. |
 | `--persist [<path>]` | off | Keep the SQLite index on disk between runs so a restart only re-parses files that actually changed. Bare `--persist` caches at `<root>/.dirsql/cache.db`; `--persist <path>` caches at `<path>`. Off by default (the index is ephemeral). Also available on [`dirsql query`](#dirsql-query). See [Keep the index across restarts](../howto/persist.md). |
+| `--no-ignore` | off | Scan files a `.gitignore` would hide. [Path-tables](./path-tables.md#skip-rules) respect `.gitignore` files by default; this flag restores the full walk. The built-in skips (`node_modules`/`.git`) and configured `ignore` patterns still apply. Also available on [`dirsql query`](#dirsql-query). |
 | `--extension <path>` | none | Load a SQLite extension by literal path, overriding the config's `[[dirsql.extension]]` entries. Repeatable. Format: `<path>` or `<path>::<entrypoint>`. Internal plumbing for the pip/npm launchers, which resolve package-name extensions and pass the resolved paths here — not intended for direct use. When any `--extension` is present, the config file's own extension entries are not loaded. |
 | `--version` | | Print the version and exit. |
 | `--help` | | Print usage and exit. |
@@ -163,6 +164,8 @@ uses**, so behavior is identical to `POST /query` by construction:
   on-disk cache. Because its value is optional, place a bare `--persist` after
   the SQL (`dirsql query "SELECT …" --persist`) or use the `=` form
   (`--persist=/path`) so it does not swallow the SQL argument.
+- **`--no-ignore`** is honored: path-tables in the query scan files a
+  `.gitignore` would hide. See [Skip rules](./path-tables.md#skip-rules).
 - **Hooks** ([`pre-query`](./hooks.md#pre-query) /
   [`post-query`](./hooks.md#post-query)) and the
   [`[dirsql].hook-timeout`](./config.md#dirsql-keys) apply identically.

package/docs/reference/path-tables.md

@@ -179,19 +179,48 @@ A path-table scan applies the same [`ignore`](/reference/config) patterns your
 declared tables use, plus two built-in defaults so a zero-config
 `SELECT * FROM './'` does not drown in machinery:
 
-- `node_modules/**`
-- `.git/**`
+- `**/node_modules/**`
+- `**/.git/**`
+
+Both apply at any depth, so a `node_modules` nested inside a subdirectory is
+skipped just like one at the top.
+
+### `.gitignore`
+
+Path-table scans also respect `.gitignore` files by default, the way fd and
+ripgrep do: a `.gitignore` anywhere in the tree applies below its own
+directory, deeper files override shallower ones, `!pattern` re-includes, and
+an ignored directory is pruned rather than walked. In a typical repo this
+excludes build output, virtualenvs, and caches with zero ceremony. No `.git`
+directory is required — a `.gitignore` in any scanned directory counts — and
+the built-in defaults above remain as a floor for directories with no
+`.gitignore` at all.
+
+Pass [`--no-ignore`](./cli.md#flags) to restore the full walk — the
+determinism switch for scripted use, since results otherwise depend on
+`.gitignore` state. It disables only the `.gitignore` respect; the built-in
+defaults and configured `ignore` patterns still apply.
+
+### Naming a skipped directory
 
 Skip rules are judged on the part of the path *below* what you named outright,
-so pointing at a skipped directory still scans it:
+so pointing at a skipped directory — built-in or gitignored — still scans it:
 
 ```sql
 SELECT path FROM './';                     -- no node_modules rows
 SELECT path FROM './node_modules/*/package.json';  -- scans it anyway
+SELECT path FROM './dist';                 -- scans dist/ even when gitignored
 ```
 
-Dotfiles are ordinary files: `'./'` and `'./*'` include them. Add an `ignore`
-pattern if you would rather not see them.
+A `.gitignore` at or below the directory you named still filters beneath it;
+only rules inherited from above it are set aside.
+
+### Hidden files
+
+Dotfiles are ordinary files: `'./'` and `'./*'` include them, with or without
+`--no-ignore`. This is a deliberate divergence from fd/ripgrep — querying
+dotfile directories (`.claude/`, …) is a first-class `dirsql` use case. Add an
+`ignore` pattern if you would rather not see them.
 
 ## Joining against declared tables
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dirsql",
-  "version": "0.4.6",
+  "version": "0.4.8",
   "description": "Ephemeral SQL index over a local directory",
   "license": "MIT",
   "repository": "https://github.com/thekevinscott/dirsql",
@@ -212,15 +212,15 @@
     ]
   },
   "optionalDependencies": {
-    "@dirsql/lib-linux-x64-gnu": "0.4.6",
-    "@dirsql/lib-linux-arm64-gnu": "0.4.6",
-    "@dirsql/lib-darwin-x64": "0.4.6",
-    "@dirsql/lib-darwin-arm64": "0.4.6",
-    "@dirsql/lib-win32-x64-msvc": "0.4.6",
-    "@dirsql/cli-linux-x64-gnu": "0.4.6",
-    "@dirsql/cli-linux-arm64-gnu": "0.4.6",
-    "@dirsql/cli-darwin-x64": "0.4.6",
-    "@dirsql/cli-darwin-arm64": "0.4.6",
-    "@dirsql/cli-win32-x64-msvc": "0.4.6"
+    "@dirsql/lib-linux-x64-gnu": "0.4.8",
+    "@dirsql/lib-linux-arm64-gnu": "0.4.8",
+    "@dirsql/lib-darwin-x64": "0.4.8",
+    "@dirsql/lib-darwin-arm64": "0.4.8",
+    "@dirsql/lib-win32-x64-msvc": "0.4.8",
+    "@dirsql/cli-linux-x64-gnu": "0.4.8",
+    "@dirsql/cli-linux-arm64-gnu": "0.4.8",
+    "@dirsql/cli-darwin-x64": "0.4.8",
+    "@dirsql/cli-darwin-arm64": "0.4.8",
+    "@dirsql/cli-win32-x64-msvc": "0.4.8"
   }
 }