From 792b834cbe2013ba3a4e97c30d581506363ed60d Mon Sep 17 00:00:00 2001 From: ergosteur <1992147+ergosteur@users.noreply.github.com> Date: Fri, 14 Aug 2026 12:02:41 -0400 Subject: [PATCH] docs: add a JDownloader quick reference Covers why fetching goes through JDownloader rather than Instaloader (the instagram.com vs CDN split, and what the metadata gap actually costs), the settings that matter, cookie handling, the two-URL workflow, jd2-sync usage, the expected on-disk layout, and what to do when something breaks. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_011uBWhwV3wFQ5MBCcMHHem7 --- CLAUDE.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 06fd643..3c82d42 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -16,7 +16,8 @@ InstaArchive Viewer is a React 19 + Vite 6 PWA for browsing archived Instagram d - `npm test` / `npm run test:watch` — vitest - `npx vitest run src/lib/archive-patterns.test.ts` — a single test file - `npm run jd2 -- --archives --dry-run` — generate JDownloader `.crawljob` - files for every profile on disk (see `scripts/jd2-sync.ts`) + files for every profile on disk (see `scripts/jd2-sync.ts` and + `docs/jdownloader.md`) Local development usually needs both `npm run dev` and `npm run server`. Local-folder mode works without the backend; server-mode archives do not.