Use `build/routes.json` instead of scraping many docs pages for `/rsshub/routes`

[black-backdoor]

Routes

/rsshub/routes/:lang?

Full routes

/rsshub/routes/en

Related documentation

https://docs.rsshub.app/routes/program-update#new-routes

What is expected?

The current route implementation for /rsshub/routes scrapes many documentation pages and uses a hard-coded types list. This is inefficient and brittle. I propose reading the pre-built build/routes.json (see possible alternative below) instead of scraping each category page. I couldn't open a PR for this because I don't yet understand the full RSSHub build process.

Possible alternative
https://raw.githubusercontent.com/DIYgod/RSSHub/refs/heads/gh-pages/build/routes.json

What is actually happening?

Source:
https://github.com/DIYgod/RSSHub/blob/d5cd095599177ac48c774719ad4094967f074030/lib/routes/rsshub/routes.ts

Existing Code:

async function handler(ctx) {
    const isEnglish = ctx.req.param('lang') !== 'zh';

    const lang = isEnglish ? '' : 'zh/';
    const types = [
        'social-media',
        'new-media',
        // ...
        'journal',
        'finance',
        'other',
    ];
    const all = await Promise.all(
        types.map(async (type) => {
            const response = await ofetch(`https://docs.rsshub.app/${lang}routes/${type}`);

            const $ = cheerio.load(response);
            const page = $('.page').toArray();
            const item = $('.routeBlock').toArray();
            return { page, item, type };
        })
    );
    const list = all.flatMap(({ page, item, type }) => item.map((item) => ({ page, item, type })));

    return {
        title: isEnglish ? 'RSSHub has new routes' : 'RSSHub 有新路由啦',
        link: 'https://docs.rsshub.app',
        // ...
    };
}

Deployment information

Self-hosted

Deployment information (for self-hosted)

No response

Additional info

-

This is not a duplicated issue

• I have searched existing issues to ensure this bug has not already been reported

[github-actions]

Searching for maintainers:

• /rsshub/routes/:lang?: @DIYgod

To maintainers: if you are not willing to be disturbed, list your username in scripts/workflow/test-issue/call-maintainer.js. In this way, your username will be wrapped in an inline code block when tagged so you will not be notified.

If all routes can not be found, the issue will be closed automatically. Please use NOROUTE for a route-irrelevant issue or leave a comment if it is a mistake.
如果所有路由都无法匹配，issue 将会被自动关闭。如果 issue 和路由无关，请使用 NOROUTE 关键词，或者留下评论。我们会重新审核。

[dosubot]

Hi @black-backdoor! I'm Dosu and I’m helping the RSSHub team.

You can update the /rsshub/routes endpoint to use the pre-built build/routes.json file instead of scraping documentation pages. The RSSHub build process generates this file using the scripts/workflow/build-routes.ts script, which collects all route metadata from the codebase and writes it to assets/build/routes.json during every build. In production and self-hosted deployments, this file is available for direct import and use by route handlers, making it much more efficient and robust than repeated HTTP requests and HTML parsing source.

To implement this, modify the /rsshub/routes handler to read and parse build/routes.json (or the JS module version if needed), filter or format the data as required (e.g., by language), and construct the response from this structured data. This approach avoids the brittle scraping logic and leverages the centralized route registry already generated at build time source.

For self-hosted setups, ensure your build process runs the route index generation script so build/routes.json is present and up-to-date. If you add custom routes, you’ll need to rebuild the index file by running the build script again source.

Let me know if you want a sample code snippet or details on how to structure the handler logic!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}