A comprehensive guide to testing your LNReader plugins using the web interface.
-
Start the development server:
npm run dev:start
-
Open your browser: Navigate to localhost:3000
-
Select a plugin: Use the dropdown in the top navigation bar to select the plugin you want to test.
The testing website provides five tabs to test different plugin functions:
- Popular - Test
popularNovels(), including itsLatest/Populartoggle, page-by-page fetching, and filters (via theFiltersbutton, when the plugin declares any) - Search - Test
searchNovels()with search queries - Parse Novel - Test
parseNovel()with a novel path. If the plugin setstotalPages(see Pagination), this tab also exercisesparsePage()through Previous/Next/Fetch Page controls, and offers an "Export EPUB" button that fetches every page's chapters (viaparsePage, when paginated) and each one's content (viaparseChapter) into a downloadable EPUB file - Parse Chapter - Test
parseChapter()with a chapter path - Settings - Playground-wide request configuration: the browser User-Agent (and whether to
send it), extra cookies to attach to every request, and the fetch mode (Proxy/Node
Fetch/Curl) used to reach the target site. This is a testing convenience for the playground
itself, separate from a plugin's own
pluginSettings
Before submitting your plugin, verify that:
- All five tabs work without errors
- Multiple pages load correctly, for both
popularNovelsand, if implemented,parsePage - Search returns accurate results
- Novel parsing extracts all metadata
- Chapter content is clean
- Filters work (if implemented)
- No console errors appear
- Paths are properly formatted
- Images load correctly
- Plugin Development: See docs.md for API reference
- Quick Start: See quickstart.md for plugin creation
- Pre-PR Check: See testing.md for the required
npm run check:pluginlive check - Issues: Create a GitHub issue
- Community: Join us on Discord