Router for what? How it works?

At a glance

The community member created a new crawler using the Crawlee library, which generated a router.js file with a default handler that enqueues new URLs with the 'detail' label. The community member then added a handler for the 'detail' route, which logs the page title and saves the URL and title to a dataset.

The community member's question is how to call or invoke the router without using the enqueueLinks function, and where they can see the functions that the 'ctx' object in the default handler admits.

In the comments, other community members explain that the router is used to handle different types of requests based on the label assigned to them. They suggest that to create a flow like the one in the code snippet, the community member should enqueue the next request with the next route label in each route handler.

One community member also provides more details on how the RequestQueue and Router work together, explaining that the Router only processes requests from the RequestQueue, and that the processing of a request starts and ends within a single RequestHandler.

There is no explicitly marked answer in the comments.

Useful resources

ssmasher

I created a new crawler using the npx crawlee create project command, that creates some folders and files, it creates me a router.js file, which it has an instance of createPlaywrightRouter

Plain Text

export const router = createPlaywrightRouter();

router.addDefaultHandler(async ({ enqueueLinks, log }) => {
    log.info(`enqueueing new URLs`);
    await enqueueLinks({
        globs: ['https://crawlee.dev/**'],
        label: 'detail',
    });
});

router.addHandler('detail', async ({ request, page, log }) => {
    const title = await page.title();
    log.info(`${title}`, { url: request.loadedUrl });

    await Dataset.pushData({
        url: request.loadedUrl,
        title,
    });
});

as I understand, you are creating the default handler which is kinda the "main" listener, so later you are calling/invoking your route "detail", for the enqueLinks function, this could be interesting to split your process in more "routes"/steps, so it can be more clean and decoupled later.
My question is, how to call or invoke this without the enqueList function?
I was expecting something like:

Plain Text

router.addDefaultHandler(async (ctx) => {
    await ctx.invoke('extract-meta-data')
    await ctx.invoke('extract-detail')
    await ctx.invoke('download-files')
});

Where can I see the functions this CTX admit or maybe I understood the router totally different.
Thanks 🙂