@youtyan/code-viewer 0.6.8 → 0.6.10
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/README.md +14 -2
- package/dist/code-viewer.js +792 -183
- package/package.json +1 -1
- package/skills/code-viewer-query/SKILL.md +3 -1
- package/web/app.js +302 -121
- package/web/style.css +3 -0
package/README.md
CHANGED
|
@@ -34,6 +34,8 @@ Requires Node.js 20 or newer when installed from npm. Development uses
|
|
|
34
34
|
viewer.
|
|
35
35
|
- Browse SQLite, PostgreSQL, MySQL, Redis, Elasticsearch, and S3-compatible
|
|
36
36
|
object storage (MinIO, LocalStack) with a built-in datastore viewer.
|
|
37
|
+
Local Supabase CLI (`supabase start`) Postgres projects are auto-discovered
|
|
38
|
+
too, without needing a `docker-compose.yml`.
|
|
37
39
|
- Read the built-in Help page for getting started, the `.code-viewer/`
|
|
38
40
|
project files, AI annotations, datastores, the agent skill, and
|
|
39
41
|
keybindings.
|
|
@@ -42,8 +44,9 @@ Requires Node.js 20 or newer when installed from npm. Development uses
|
|
|
42
44
|
`@youtyan/code-viewer` version and execution origin (npx cache vs
|
|
43
45
|
local), SQLite driver and snapshot store, Git, discovery summary,
|
|
44
46
|
per-source datastore connectivity (each discovered SQLite / docker
|
|
45
|
-
SQL / Redis / Elasticsearch / S3 source gets one row
|
|
46
|
-
minimal-read probe; failure rows include a paste-safe retry
|
|
47
|
+
SQL / Supabase CLI / Redis / Elasticsearch / S3 source gets one row
|
|
48
|
+
with a 2s minimal-read probe; failure rows include a paste-safe retry
|
|
49
|
+
hint),
|
|
47
50
|
Docker / Compose health (config dry-parse + `compose ps` per service),
|
|
48
51
|
and the listening port. Useful when `npx` cache mismatch (e.g.
|
|
49
52
|
`NODE_MODULE_VERSION` errors) needs a remediation hint, or when a
|
|
@@ -219,6 +222,15 @@ Services whose names collide across subdirectories are kept distinct via
|
|
|
219
222
|
`docker:<service>@<relDir>` ids (cwd-direct compose files keep the historical
|
|
220
223
|
`docker:<service>` id for backward compatibility).
|
|
221
224
|
|
|
225
|
+
**Supabase CLI** (`supabase start`) local projects are also auto-discovered,
|
|
226
|
+
even though the Supabase CLI does not write a `docker-compose.yml` into the
|
|
227
|
+
project directory. Any `supabase/config.toml` found by the same recursive scan
|
|
228
|
+
is picked up (`project_id` and `[db] port` are read from it), and the running
|
|
229
|
+
Postgres container is resolved directly via `docker ps` (matched by container
|
|
230
|
+
name and the `com.supabase.cli.project` label) instead of `docker compose ps`.
|
|
231
|
+
Connection defaults to the Supabase CLI's documented local credentials
|
|
232
|
+
(`postgres`/`postgres`/`postgres`).
|
|
233
|
+
|
|
222
234
|
**Redis** support: browse DB 0–15, SCAN keys, and view values per
|
|
223
235
|
type (string/hash/list as dedicated panes, set/zset/stream as JSON views).
|
|
224
236
|
Edit values, delete keys, and create new keys (string/hash/list/set/zset/stream)
|