How volcyano42/novel-downloader works
Novel-downloader supports CLI and web clients for searching novels, selecting sources, downloading chapters, managing a bookshelf/reader, and exporting books. Its central web path routes frontend requests through FastAPI task and engine management into source-specific parsers, then persists chapter data for bookshelf and reading operations. The CLI is a separate user entry into the shared library. README navigation names source capabilities and configuration as major features; frontend details and several router interactions are inferred from the tree, so only documented or indexed relationships are solidly connected.
Main entry points: main.py FastAPI app · client.ts API client · storage.py Bookshelf API · engine_manager.py Engine manager
Components 25
User interfaces
- Reader
frontend/src/features/reader/Reader.tsx - Bookshelf UI
frontend/src/features/bookshelf/BookshelfPage.tsx - Book details
frontend/src/features/detail/DetailPage.tsx - Web UI
frontend/src/App.tsx - CLI
cli/main.py
Web application
- API client
frontend/src/api/client.ts - FastAPI app
backend/main.py - Download API
backend/routers/download.py - Task manager
backend/services/task_manager.py - Engine manager
backend/services/engine_manager.py - Export API
backend/routers/export.py - Config API
backend/routers/config.py - History API
backend/routers/history.py - Bookshelf API
backend/routers/storage.py
Novel runtime
- Download workflow
novelbase/core/downloader.py - Fetch engines
novelbase/core/engine.py - Novel models
novelbase/models/novel.py - Novel storage
novelbase/core/storage.py - Book exporters
novelbase/exporter.py
Source adapters
- Source registry
novelbase/source.py - Source manifests
novelbase/sources/manifest.py - Source adapters
novelbase/sources
Configuration and data
- Runtime config
shared/config.py - User library data
shared/user_data.py
Other components
- User
Connections 32
- User → Web UI: uses
- User → CLI: runs
- Web UI → API client: requests
- API client → FastAPI app: HTTP calls
- FastAPI app → Download API: mounts
backend/main.py - FastAPI app → Export API: mounts
backend/main.py - FastAPI app → Config API: mounts
backend/main.py - FastAPI app → History API: mounts
backend/main.py - FastAPI app → Bookshelf API: mounts
backend/main.py - Download API → Task manager: manages tasks
backend/routers/download.py - Download API → Engine manager: requests engines
backend/routers/download.py - Task manager → Engine manager: gets engines
backend/services/task_manager.py - Task manager → Novel storage: creates store
backend/services/task_manager.py - Engine manager → Runtime config: loads settings
backend/services/engine_manager.py - Engine manager → Fetch engines: creates engine
backend/services/engine_manager.py - Fetch engines → Source registry: dispatches capabilities
- Source registry → Source manifests: loads manifests
novelbase/source.py - Source registry → Source adapters: loads adapter
novelbase/source.py - CLI → Download workflow: calls workflows
cli/main.py - Download workflow → Fetch engines: fetches source data
novelbase/__init__.py - Download workflow → Novel models: builds results
- Export API → Novel storage: reads book data
backend/routers/export.py - Export API → Book exporters: selects format
backend/routers/export.py - Bookshelf API → Novel storage: reads and writes
backend/routers/storage.py - Bookshelf API → User library data: tracks sources
backend/routers/storage.py - History API → User library data: reads history
backend/routers/history.py - Config API → Runtime config: reads settings
backend/routers/config.py - Config API → Source registry: validates sources
backend/routers/config.py - Bookshelf UI → API client: requests data
- Book details → API client: requests details
- Reader → API client: requests chapters
- Bookshelf API → Novel models: serializes metadata
backend/routers/storage.py