dirsql 0.3.18__tar.gz → 0.3.20__tar.gz

{dirsql-0.3.18 → dirsql-0.3.20}/Cargo.lock

@@ -499,7 +499,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.3.18"
+version = "0.3.20"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.3.18 → dirsql-0.3.20}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.3.18
+Version: 0.3.20
 Requires-Dist: pytest>=8 ; extra == 'dev'
 Requires-Dist: pytest-describe>=2 ; extra == 'dev'
 Requires-Dist: pytest-asyncio>=0.23 ; extra == 'dev'

{dirsql-0.3.18/packages/python → dirsql-0.3.20}/docs/AGENTS.md

@@ -45,11 +45,19 @@ The docs follow the [Diataxis](https://diataxis.fr/) framework:
 The **CLI** (`cli/`) is a self-contained section reachable from its own
 top-level `CLI` nav tab, with a path-scoped sidebar (`/cli/` key in
 `config.ts`). Everything a CLI user needs -- installation, running the server,
-`init`, the `.dirsql.toml` config file, and the HTTP API -- lives under
-`cli/`. Do not move CLI pages back into `guide/`.
+`init`, config files (`.dirsql.toml` or native-language), and the HTTP API --
+lives under `cli/`. Do not move CLI pages back into `guide/`.
 
 ## Conventions
 
+- **Lead with the use case.** Open each feature description with *why* a
+  reader would reach for it before *how* it works. Don't frame a feature
+  by what an adjacent feature can't do.
+  *Don't:* "`.dirsql.toml` can't parse contents — you need code in
+  `extract`. Point `--config` at a Python module..."
+  *Do:* "Native-language configs let you build tables from the
+  *contents* of files — frontmatter, JSON values, CSV cells — by
+  writing a dynamic `extract` callback."
 - Wrap `dirsql` in backticks in all prose text
 - Use VitePress [code group](https://vitepress.dev/guide/markdown#code-groups) syntax (`::: code-group`) for multi-language examples with `Python`, `Rust`, and `TypeScript` tabs
 - Internal links use relative paths (e.g., `./guide/tables.md`)

{dirsql-0.3.18/packages/rust → dirsql-0.3.20}/docs/cli/config.md

@@ -6,7 +6,10 @@ canonical: https://thekevinscott.github.io/dirsql/cli/config
 
 > Online: <https://thekevinscott.github.io/dirsql/cli/config>
 
-`dirsql` can be configured with an optional `.dirsql.toml` file (if omitted, server falls back to [defaults](./server.md#defaults)). `.dirsql.toml` defines how files are parsed into SQL tables.
+`dirsql` can be configured with an optional config file (if omitted, server falls back to [defaults](./server.md#defaults)). Two formats are accepted:
+
+- **`dirsql.toml`** — declarative; covers filesystem-fact tables. Works with any installation.
+- **`.py` / `.js`** — native-language; lets you write `extract` callbacks in Python or JavaScript. CLI-only, and only the launcher matching the file's language can run it. See [Native-Language Configs](#native-language-configs).
 
 ## Basic Example
 
@@ -172,10 +175,76 @@ ddl  = "CREATE TABLE logs (_path TEXT, _size INTEGER, _mtime INTEGER)"
 glob = "logs/*.csv"
 ```
 
-## When you need parsed content
+## Native-Language Configs
+
+You can provide a config file in a particular language, allowing you to define a dynamic extract function. This can be useful for building a database based on the _contents_ of a file.
+
+```bash
+dirsql --config dirsql.config.py
+dirsql --config dirsql.config.js
+```
+
+The file looks exactly like the in-process SDK construction — same
+`DirSQL` / `Table` API:
+
+::: code-group
+
+```python [dirsql.config.py]
+import json
+from dirsql import DirSQL, Table
+
+def extract_meta(path):
+    with open(path) as f:
+        return [json.load(f)]
+
+# Python must export an `app` variable
+app = DirSQL(
+    tables=[
+        Table(
+            ddl="CREATE TABLE papers (title TEXT, _path TEXT)",
+            glob="**/meta.json",
+            extract=extract_meta,
+        ),
+    ],
+)
+```
+
+```javascript [dirsql.config.mjs]
+import { readFileSync } from "node:fs";
+import { DirSQL } from "dirsql";
+
+export default new DirSQL({
+  tables: [
+    {
+      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
+      glob: "**/meta.json",
+      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
+    },
+  ],
+});
+```
+
+```javascript [dirsql.config.cjs]
+const { readFileSync } = require("node:fs");
+const { DirSQL } = require("dirsql");
+
+module.exports = new DirSQL({
+  tables: [
+    {
+      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
+      glob: "**/meta.json",
+      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
+    },
+  ],
+});
+```
+
+:::
+
+Only the extension matters — the file can be named anything. `dirsql.config.{py,mjs,cjs}` is the suggested convention but not required.
+
+### Module conventions
 
-`.dirsql.toml` does not parse file contents. For columns derived from the
-*inside* of files (frontmatter keys, JSON values, CSV cells, etc.),
-register a programmatic [`Table`](../guide/tables.md) instead, and parse the
-bytes in your host language. Glob captures and stat virtuals are still
-auto-injected into rows produced by your extract.
+- **Python (`.py`)** — module-level `app = DirSQL(...)`.
+- **ESM (`.mjs`, or `.js` in an ESM package)** — `export default new DirSQL(...)`.
+- **CommonJS (`.cjs`, or `.js` in a CJS package)** — `module.exports = new DirSQL(...)`.

{dirsql-0.3.18/packages/rust → dirsql-0.3.20}/docs/cli/index.md

@@ -10,16 +10,17 @@ canonical: https://thekevinscott.github.io/dirsql/cli/
 the same indexing, querying, and watching functionality as the SDK — no host
 language required. Run it in any directory to query your files over HTTP:
 with no config it serves a default `files` table, and a
-[`.dirsql.toml`](./config.md) config defines custom tables.
+[config file](./config.md) defines custom tables.
 
 Everything you need to run `dirsql` as a CLI lives in this section:
 
 - **[Installation](#installation)** — get the `dirsql` binary.
 - **[Running the Server](./server.md)** — subcommands and flags.
 - **[Generating a Config (`init`)](./init.md)** — scaffold a `.dirsql.toml`.
-- **[Configuration File](./config.md)** — the `.dirsql.toml` format. Custom
-  tables are defined exclusively through this file; without it, the server
-  runs in [zero-config mode](./server.md#zero-config-mode).
+- **[Configuration File](./config.md)** — the `.dirsql.toml` format and the
+  `.py` / `.js` native-language alternative. Custom tables
+  are defined through a config file; without one, the server runs in
+  [zero-config mode](./server.md#zero-config-mode).
 - **[HTTP API](./http-api.md)** — the `POST /query` and `GET /events`
   endpoints, status codes, and event streaming.
 

{dirsql-0.3.18/packages/rust → dirsql-0.3.20}/docs/cli/server.md

@@ -26,8 +26,10 @@ dirsql
 $ Running at localhost:7117
 ```
 
-The server reads tables from a [`.dirsql.toml`](./config.md) config file. By
-default it looks for `./.dirsql.toml`; override the path with `--config`.
+The server reads tables from a [config file](./config.md). By default it
+looks for `./.dirsql.toml`; pass `--config <path>` to point at a different
+`.toml` file or a [native-language config](./config.md#native-language-configs)
+(`.py` / `.js`).
 
 ## Defaults
 
@@ -45,13 +47,13 @@ curl -s localhost:7117/query -H 'content-type: application/json' \
   -d '{"sql":"SELECT _basename, _size FROM files ORDER BY _size DESC LIMIT 5"}'
 ```
 
-A `.dirsql.toml` file will override the default.
+A config file will override the default.
 
 ## Flags
 
 | Flag | Default | Description |
 |---|---|---|
-| `--config <path>` | `./.dirsql.toml` | Path to the config file. The index is rooted at the directory containing this file. |
+| `--config <path>` | `./.dirsql.toml` | Path to the config file (`.toml` or [native-language](./config.md#native-language-configs)). The index is rooted at the directory containing this file. |
 | `--host <addr>` | `localhost` | Bind address |
 | `--port <n>` | `7117` | TCP port to bind |
 

{dirsql-0.3.18 → dirsql-0.3.20}/docs/package.json

@@ -11,7 +11,7 @@
     "test:integration": "pnpm run build && playwright test"
   },
   "devDependencies": {
-    "@playwright/test": "^1.48.0",
+    "@playwright/test": "^1.60.0",
     "vitepress": "^1.5.0",
     "vitest": "^2.1.0"
   }

{dirsql-0.3.18 → dirsql-0.3.20}/docs/pnpm-lock.yaml

@@ -9,8 +9,8 @@ importers:
   .:
     devDependencies:
       '@playwright/test':
-        specifier: ^1.48.0
-        version: 1.59.1
+        specifier: ^1.60.0
+        version: 1.60.0
       vitepress:
         specifier: ^1.5.0
         version: 1.6.4(@algolia/client-search@5.50.1)(postcss@8.5.8)(search-insights@2.17.3)
@@ -283,8 +283,8 @@ packages:
   '@jridgewell/sourcemap-codec@1.5.5':
     resolution: {integrity: sha512-cYQ9310grqxueWbl+WuIUIaiUaDcj7WOq5fVhEljNVgRfOUhY9fy2zTvfoqWsnebh8Sl70VScFbICvJnLKB0Og==}
 
-  '@playwright/test@1.59.1':
-    resolution: {integrity: sha512-PG6q63nQg5c9rIi4/Z5lR5IVF7yU5MqmKaPOe0HSc0O2cX1fPi96sUQu5j7eo4gKCkB2AnNGoWt7y4/Xx3Kcqg==}
+  '@playwright/test@1.60.0':
+    resolution: {integrity: sha512-O71yZIbAh/PxDMNGns37GHBIfrVkEVyn+AXyIa5dOTfb4/xNvRWV+Vv/NMbNCtODB/pO7vLlF2OTmMVLhmr7Ag==}
     engines: {node: '>=18'}
     hasBin: true
 
@@ -774,13 +774,13 @@ packages:
   picocolors@1.1.1:
     resolution: {integrity: sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==}
 
-  playwright-core@1.59.1:
-    resolution: {integrity: sha512-HBV/RJg81z5BiiZ9yPzIiClYV/QMsDCKUyogwH9p3MCP6IYjUFu/MActgYAvK0oWyV9NlwM3GLBjADyWgydVyg==}
+  playwright-core@1.60.0:
+    resolution: {integrity: sha512-9bW6zvX/m0lEbgTKJ6YppOKx8H3VOPBMOCFh2irXFOT4BbHgrx5hPjwJYLT40Lu+4qtD36qKc/Hn56StUW57IA==}
     engines: {node: '>=18'}
     hasBin: true
 
-  playwright@1.59.1:
-    resolution: {integrity: sha512-C8oWjPR3F81yljW9o5OxcWzfh6avkVwDD2VYdwIGqTkl+OGFISgypqzfu7dOe4QNLL2aqcWBmI3PMtLIK233lw==}
+  playwright@1.60.0:
+    resolution: {integrity: sha512-hheHdokM8cdqCb0lcE3s+zT4t4W+vvjpGxsZlDnikarzx8tSzMebh3UiFtgqwFwnTnjYQcsyMF8ei2mCO/tpeA==}
     engines: {node: '>=18'}
     hasBin: true
 
@@ -1206,9 +1206,9 @@ snapshots:
 
   '@jridgewell/sourcemap-codec@1.5.5': {}
 
-  '@playwright/test@1.59.1':
+  '@playwright/test@1.60.0':
     dependencies:
-      playwright: 1.59.1
+      playwright: 1.60.0
 
   '@rollup/rollup-android-arm-eabi@4.60.1':
     optional: true
@@ -1686,11 +1686,11 @@ snapshots:
 
   picocolors@1.1.1: {}
 
-  playwright-core@1.59.1: {}
+  playwright-core@1.60.0: {}
 
-  playwright@1.59.1:
+  playwright@1.60.0:
     dependencies:
-      playwright-core: 1.59.1
+      playwright-core: 1.60.0
     optionalDependencies:
       fsevents: 2.3.2
 

{dirsql-0.3.18 → dirsql-0.3.20}/packages/python/Cargo.toml

@@ -4,7 +4,7 @@ name = "dirsql-py-ext"
 # pypi/maturin handler can rewrite it via `write-version` before
 # `maturin build`. `pyproject.toml` declares `dynamic = ["version"]`
 # and maturin reads this field. Mirrors `packages/rust/Cargo.toml`.
-version = "0.3.18"
+version = "0.3.20"
 edition.workspace = true
 publish = false
 readme = "README.md"

{dirsql-0.3.18 → dirsql-0.3.20}/packages/python/conftest.py

@@ -8,7 +8,7 @@ imports real types from `dirsql._dirsql`.
 
 The stub is installed ONLY when the real extension can't be imported.
 When `maturin develop` has been run (as in CI), the real extension wins
-and tests that depend on it — `test_async.py`, the integration suites —
+and tests that depend on it — `_async_test.py`, the integration suites —
 see the real bindings.
 """
 

{dirsql-0.3.18 → dirsql-0.3.20/packages/python}/docs/AGENTS.md

@@ -45,11 +45,19 @@ The docs follow the [Diataxis](https://diataxis.fr/) framework:
 The **CLI** (`cli/`) is a self-contained section reachable from its own
 top-level `CLI` nav tab, with a path-scoped sidebar (`/cli/` key in
 `config.ts`). Everything a CLI user needs -- installation, running the server,
-`init`, the `.dirsql.toml` config file, and the HTTP API -- lives under
-`cli/`. Do not move CLI pages back into `guide/`.
+`init`, config files (`.dirsql.toml` or native-language), and the HTTP API --
+lives under `cli/`. Do not move CLI pages back into `guide/`.
 
 ## Conventions
 
+- **Lead with the use case.** Open each feature description with *why* a
+  reader would reach for it before *how* it works. Don't frame a feature
+  by what an adjacent feature can't do.
+  *Don't:* "`.dirsql.toml` can't parse contents — you need code in
+  `extract`. Point `--config` at a Python module..."
+  *Do:* "Native-language configs let you build tables from the
+  *contents* of files — frontmatter, JSON values, CSV cells — by
+  writing a dynamic `extract` callback."
 - Wrap `dirsql` in backticks in all prose text
 - Use VitePress [code group](https://vitepress.dev/guide/markdown#code-groups) syntax (`::: code-group`) for multi-language examples with `Python`, `Rust`, and `TypeScript` tabs
 - Internal links use relative paths (e.g., `./guide/tables.md`)

{dirsql-0.3.18 → dirsql-0.3.20/packages/python}/docs/cli/config.md

@@ -6,7 +6,10 @@ canonical: https://thekevinscott.github.io/dirsql/cli/config
 
 > Online: <https://thekevinscott.github.io/dirsql/cli/config>
 
-`dirsql` can be configured with an optional `.dirsql.toml` file (if omitted, server falls back to [defaults](./server.md#defaults)). `.dirsql.toml` defines how files are parsed into SQL tables.
+`dirsql` can be configured with an optional config file (if omitted, server falls back to [defaults](./server.md#defaults)). Two formats are accepted:
+
+- **`dirsql.toml`** — declarative; covers filesystem-fact tables. Works with any installation.
+- **`.py` / `.js`** — native-language; lets you write `extract` callbacks in Python or JavaScript. CLI-only, and only the launcher matching the file's language can run it. See [Native-Language Configs](#native-language-configs).
 
 ## Basic Example
 
@@ -172,10 +175,76 @@ ddl  = "CREATE TABLE logs (_path TEXT, _size INTEGER, _mtime INTEGER)"
 glob = "logs/*.csv"
 ```
 
-## When you need parsed content
+## Native-Language Configs
+
+You can provide a config file in a particular language, allowing you to define a dynamic extract function. This can be useful for building a database based on the _contents_ of a file.
+
+```bash
+dirsql --config dirsql.config.py
+dirsql --config dirsql.config.js
+```
+
+The file looks exactly like the in-process SDK construction — same
+`DirSQL` / `Table` API:
+
+::: code-group
+
+```python [dirsql.config.py]
+import json
+from dirsql import DirSQL, Table
+
+def extract_meta(path):
+    with open(path) as f:
+        return [json.load(f)]
+
+# Python must export an `app` variable
+app = DirSQL(
+    tables=[
+        Table(
+            ddl="CREATE TABLE papers (title TEXT, _path TEXT)",
+            glob="**/meta.json",
+            extract=extract_meta,
+        ),
+    ],
+)
+```
+
+```javascript [dirsql.config.mjs]
+import { readFileSync } from "node:fs";
+import { DirSQL } from "dirsql";
+
+export default new DirSQL({
+  tables: [
+    {
+      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
+      glob: "**/meta.json",
+      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
+    },
+  ],
+});
+```
+
+```javascript [dirsql.config.cjs]
+const { readFileSync } = require("node:fs");
+const { DirSQL } = require("dirsql");
+
+module.exports = new DirSQL({
+  tables: [
+    {
+      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
+      glob: "**/meta.json",
+      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
+    },
+  ],
+});
+```
+
+:::
+
+Only the extension matters — the file can be named anything. `dirsql.config.{py,mjs,cjs}` is the suggested convention but not required.
+
+### Module conventions
 
-`.dirsql.toml` does not parse file contents. For columns derived from the
-*inside* of files (frontmatter keys, JSON values, CSV cells, etc.),
-register a programmatic [`Table`](../guide/tables.md) instead, and parse the
-bytes in your host language. Glob captures and stat virtuals are still
-auto-injected into rows produced by your extract.
+- **Python (`.py`)** — module-level `app = DirSQL(...)`.
+- **ESM (`.mjs`, or `.js` in an ESM package)** — `export default new DirSQL(...)`.
+- **CommonJS (`.cjs`, or `.js` in a CJS package)** — `module.exports = new DirSQL(...)`.

{dirsql-0.3.18 → dirsql-0.3.20/packages/python}/docs/cli/index.md

@@ -10,16 +10,17 @@ canonical: https://thekevinscott.github.io/dirsql/cli/
 the same indexing, querying, and watching functionality as the SDK — no host
 language required. Run it in any directory to query your files over HTTP:
 with no config it serves a default `files` table, and a
-[`.dirsql.toml`](./config.md) config defines custom tables.
+[config file](./config.md) defines custom tables.
 
 Everything you need to run `dirsql` as a CLI lives in this section:
 
 - **[Installation](#installation)** — get the `dirsql` binary.
 - **[Running the Server](./server.md)** — subcommands and flags.
 - **[Generating a Config (`init`)](./init.md)** — scaffold a `.dirsql.toml`.
-- **[Configuration File](./config.md)** — the `.dirsql.toml` format. Custom
-  tables are defined exclusively through this file; without it, the server
-  runs in [zero-config mode](./server.md#zero-config-mode).
+- **[Configuration File](./config.md)** — the `.dirsql.toml` format and the
+  `.py` / `.js` native-language alternative. Custom tables
+  are defined through a config file; without one, the server runs in
+  [zero-config mode](./server.md#zero-config-mode).
 - **[HTTP API](./http-api.md)** — the `POST /query` and `GET /events`
   endpoints, status codes, and event streaming.
 

{dirsql-0.3.18 → dirsql-0.3.20}/packages/python/docs/cli/server.md

@@ -26,8 +26,10 @@ dirsql
 $ Running at localhost:7117
 ```
 
-The server reads tables from a [`.dirsql.toml`](./config.md) config file. By
-default it looks for `./.dirsql.toml`; override the path with `--config`.
+The server reads tables from a [config file](./config.md). By default it
+looks for `./.dirsql.toml`; pass `--config <path>` to point at a different
+`.toml` file or a [native-language config](./config.md#native-language-configs)
+(`.py` / `.js`).
 
 ## Defaults
 
@@ -45,13 +47,13 @@ curl -s localhost:7117/query -H 'content-type: application/json' \
   -d '{"sql":"SELECT _basename, _size FROM files ORDER BY _size DESC LIMIT 5"}'
 ```
 
-A `.dirsql.toml` file will override the default.
+A config file will override the default.
 
 ## Flags
 
 | Flag | Default | Description |
 |---|---|---|
-| `--config <path>` | `./.dirsql.toml` | Path to the config file. The index is rooted at the directory containing this file. |
+| `--config <path>` | `./.dirsql.toml` | Path to the config file (`.toml` or [native-language](./config.md#native-language-configs)). The index is rooted at the directory containing this file. |
 | `--host <addr>` | `localhost` | Bind address |
 | `--port <n>` | `7117` | TCP port to bind |
 

{dirsql-0.3.18 → dirsql-0.3.20}/packages/python/docs/package.json

@@ -11,7 +11,7 @@
     "test:integration": "pnpm run build && playwright test"
   },
   "devDependencies": {
-    "@playwright/test": "^1.48.0",
+    "@playwright/test": "^1.60.0",
     "vitepress": "^1.5.0",
     "vitest": "^2.1.0"
   }

{dirsql-0.3.18 → dirsql-0.3.20}/packages/python/docs/pnpm-lock.yaml

@@ -9,8 +9,8 @@ importers:
   .:
     devDependencies:
       '@playwright/test':
-        specifier: ^1.48.0
-        version: 1.59.1
+        specifier: ^1.60.0
+        version: 1.60.0
       vitepress:
         specifier: ^1.5.0
         version: 1.6.4(@algolia/client-search@5.50.1)(postcss@8.5.8)(search-insights@2.17.3)
@@ -283,8 +283,8 @@ packages:
   '@jridgewell/sourcemap-codec@1.5.5':
     resolution: {integrity: sha512-cYQ9310grqxueWbl+WuIUIaiUaDcj7WOq5fVhEljNVgRfOUhY9fy2zTvfoqWsnebh8Sl70VScFbICvJnLKB0Og==}
 
-  '@playwright/test@1.59.1':
-    resolution: {integrity: sha512-PG6q63nQg5c9rIi4/Z5lR5IVF7yU5MqmKaPOe0HSc0O2cX1fPi96sUQu5j7eo4gKCkB2AnNGoWt7y4/Xx3Kcqg==}
+  '@playwright/test@1.60.0':
+    resolution: {integrity: sha512-O71yZIbAh/PxDMNGns37GHBIfrVkEVyn+AXyIa5dOTfb4/xNvRWV+Vv/NMbNCtODB/pO7vLlF2OTmMVLhmr7Ag==}
     engines: {node: '>=18'}
     hasBin: true
 
@@ -774,13 +774,13 @@ packages:
   picocolors@1.1.1:
     resolution: {integrity: sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==}
 
-  playwright-core@1.59.1:
-    resolution: {integrity: sha512-HBV/RJg81z5BiiZ9yPzIiClYV/QMsDCKUyogwH9p3MCP6IYjUFu/MActgYAvK0oWyV9NlwM3GLBjADyWgydVyg==}
+  playwright-core@1.60.0:
+    resolution: {integrity: sha512-9bW6zvX/m0lEbgTKJ6YppOKx8H3VOPBMOCFh2irXFOT4BbHgrx5hPjwJYLT40Lu+4qtD36qKc/Hn56StUW57IA==}
     engines: {node: '>=18'}
     hasBin: true
 
-  playwright@1.59.1:
-    resolution: {integrity: sha512-C8oWjPR3F81yljW9o5OxcWzfh6avkVwDD2VYdwIGqTkl+OGFISgypqzfu7dOe4QNLL2aqcWBmI3PMtLIK233lw==}
+  playwright@1.60.0:
+    resolution: {integrity: sha512-hheHdokM8cdqCb0lcE3s+zT4t4W+vvjpGxsZlDnikarzx8tSzMebh3UiFtgqwFwnTnjYQcsyMF8ei2mCO/tpeA==}
     engines: {node: '>=18'}
     hasBin: true
 
@@ -1206,9 +1206,9 @@ snapshots:
 
   '@jridgewell/sourcemap-codec@1.5.5': {}
 
-  '@playwright/test@1.59.1':
+  '@playwright/test@1.60.0':
     dependencies:
-      playwright: 1.59.1
+      playwright: 1.60.0
 
   '@rollup/rollup-android-arm-eabi@4.60.1':
     optional: true
@@ -1686,11 +1686,11 @@ snapshots:
 
   picocolors@1.1.1: {}
 
-  playwright-core@1.59.1: {}
+  playwright-core@1.60.0: {}
 
-  playwright@1.59.1:
+  playwright@1.60.0:
     dependencies:
-      playwright-core: 1.59.1
+      playwright-core: 1.60.0
     optionalDependencies:
       fsevents: 2.3.2
 

{dirsql-0.3.18/packages/python → dirsql-0.3.20/packages/rust}/docs/cli/config.md

@@ -6,7 +6,10 @@ canonical: https://thekevinscott.github.io/dirsql/cli/config
 
 > Online: <https://thekevinscott.github.io/dirsql/cli/config>
 
-`dirsql` can be configured with an optional `.dirsql.toml` file (if omitted, server falls back to [defaults](./server.md#defaults)). `.dirsql.toml` defines how files are parsed into SQL tables.
+`dirsql` can be configured with an optional config file (if omitted, server falls back to [defaults](./server.md#defaults)). Two formats are accepted:
+
+- **`dirsql.toml`** — declarative; covers filesystem-fact tables. Works with any installation.
+- **`.py` / `.js`** — native-language; lets you write `extract` callbacks in Python or JavaScript. CLI-only, and only the launcher matching the file's language can run it. See [Native-Language Configs](#native-language-configs).
 
 ## Basic Example
 
@@ -172,10 +175,76 @@ ddl  = "CREATE TABLE logs (_path TEXT, _size INTEGER, _mtime INTEGER)"
 glob = "logs/*.csv"
 ```
 
-## When you need parsed content
+## Native-Language Configs
+
+You can provide a config file in a particular language, allowing you to define a dynamic extract function. This can be useful for building a database based on the _contents_ of a file.
+
+```bash
+dirsql --config dirsql.config.py
+dirsql --config dirsql.config.js
+```
+
+The file looks exactly like the in-process SDK construction — same
+`DirSQL` / `Table` API:
+
+::: code-group
+
+```python [dirsql.config.py]
+import json
+from dirsql import DirSQL, Table
+
+def extract_meta(path):
+    with open(path) as f:
+        return [json.load(f)]
+
+# Python must export an `app` variable
+app = DirSQL(
+    tables=[
+        Table(
+            ddl="CREATE TABLE papers (title TEXT, _path TEXT)",
+            glob="**/meta.json",
+            extract=extract_meta,
+        ),
+    ],
+)
+```
+
+```javascript [dirsql.config.mjs]
+import { readFileSync } from "node:fs";
+import { DirSQL } from "dirsql";
+
+export default new DirSQL({
+  tables: [
+    {
+      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
+      glob: "**/meta.json",
+      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
+    },
+  ],
+});
+```
+
+```javascript [dirsql.config.cjs]
+const { readFileSync } = require("node:fs");
+const { DirSQL } = require("dirsql");
+
+module.exports = new DirSQL({
+  tables: [
+    {
+      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
+      glob: "**/meta.json",
+      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
+    },
+  ],
+});
+```
+
+:::
+
+Only the extension matters — the file can be named anything. `dirsql.config.{py,mjs,cjs}` is the suggested convention but not required.
+
+### Module conventions
 
-`.dirsql.toml` does not parse file contents. For columns derived from the
-*inside* of files (frontmatter keys, JSON values, CSV cells, etc.),
-register a programmatic [`Table`](../guide/tables.md) instead, and parse the
-bytes in your host language. Glob captures and stat virtuals are still
-auto-injected into rows produced by your extract.
+- **Python (`.py`)** — module-level `app = DirSQL(...)`.
+- **ESM (`.mjs`, or `.js` in an ESM package)** — `export default new DirSQL(...)`.
+- **CommonJS (`.cjs`, or `.js` in a CJS package)** — `module.exports = new DirSQL(...)`.

{dirsql-0.3.18/packages/python → dirsql-0.3.20/packages/rust}/docs/cli/index.md

@@ -10,16 +10,17 @@ canonical: https://thekevinscott.github.io/dirsql/cli/
 the same indexing, querying, and watching functionality as the SDK — no host
 language required. Run it in any directory to query your files over HTTP:
 with no config it serves a default `files` table, and a
-[`.dirsql.toml`](./config.md) config defines custom tables.
+[config file](./config.md) defines custom tables.
 
 Everything you need to run `dirsql` as a CLI lives in this section:
 
 - **[Installation](#installation)** — get the `dirsql` binary.
 - **[Running the Server](./server.md)** — subcommands and flags.
 - **[Generating a Config (`init`)](./init.md)** — scaffold a `.dirsql.toml`.
-- **[Configuration File](./config.md)** — the `.dirsql.toml` format. Custom
-  tables are defined exclusively through this file; without it, the server
-  runs in [zero-config mode](./server.md#zero-config-mode).
+- **[Configuration File](./config.md)** — the `.dirsql.toml` format and the
+  `.py` / `.js` native-language alternative. Custom tables
+  are defined through a config file; without one, the server runs in
+  [zero-config mode](./server.md#zero-config-mode).
 - **[HTTP API](./http-api.md)** — the `POST /query` and `GET /events`
   endpoints, status codes, and event streaming.