Repository navigation
Add parser for novelping.com - #3013
Merged
gamebeaker merged 2 commits intoSep 28, 2026
Merged
Conversation
novelarrow.com now redirects to novelping.com, which is back on Novelbin's layout. With no parser registered for the host, the Default Parser only found the few chapter links outside the <template> holding the chapter list. NovelpingParser reuses NovelbinParser, fetching the full list from the site's /ajax/chapter-archive on the page's own host and taking chapter titles from the link's title attribute, as the link text also holds the comment count.
rajyash2892
approved these changes
Sep 23, 2026
rajyash2892
approved these changes
Sep 23, 2026
Collaborator
|
@rajyashau thanks for your work. |
This was referenced Sep 29, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #3012
Problem
novelarrow.com now redirects to novelping.com, and the site has moved back to the old Novelbin page layout. There is no parser registered for
novelping.com, so WebToEpub falls back to the Default Parser. The chapter list on the novel page sits inside a<template>, so the Default Parser only picks up the few chapter links outside it and users get a handful of chapters instead of the whole novel.Change
Adds
NovelpingParsertoNovelfullParser.js. It extendsNovelbinParser, since the markup (title, author, genres, tags, cover, description,#chr-content, chapterh2) is the same. It differs in four places:/ajax/chapter-archive?novelId=<slug>endpoint, requested on the page's host.NovelbinParserhard-codesnovelbin.com, which no longer resolves.titleattribute, because the link text also holds the comment count (Chapter 1 Nightmare Begins 17)./novel/<slug>or/book/<slug>..js-ad-slotplaceholders are removed from chapter content, and the publisher is set to NovelPing.NovelbinParserandNovelarrowParserare unchanged. One note: the Next.js layoutNovelarrowParserwas written for no longer exists. novelarrow.com pages now 302 to novelping.com, so users end up on this parser in the browser. I leftNovelarrowParseralone in case you'd prefer to handle that separately.Testing
ExperimentalTabModeand with this change. The results are the same apart from the 4 new tests, which pass.EpubPacker :: buildEpub3ContentOpfandUtestRoyalRoadParser :: makeHiddenElementsVisiblealready fail without this change. In both runs the suite also stops atWattpadParser :: fetchExtraChapterContent, which requestss.wattpad.com.npm run lintpasses.