Table of Contents

[astanb]

Does this library have a way of generating a table of contents with clickable page numbers?

[jdfesa]

The clickable-link part is supported: give the destination a bookmark, and link to its exact name with href="#...". You can use that on the page-number text in a custom contents page.

For example, a two-page React document:

import { Document, Page, Text } from '@formepdf/react';

const doc = (
  <Document>
    <Page>
      <Text>Contents</Text>
      <Text href="#Introduction">Introduction ........ 2</Text>
    </Page>
    <Page>
      <Text bookmark="Introduction">Introduction</Text>
      <Text>Your chapter content...</Text>
    </Page>
  </Document>
);

That href becomes an internal PDF GoTo action, not a web URL. The bookmark also provides a PDF outline entry.

The distinction is clickable navigation versus automatic TOC generation: the example supplies the page number because the chapter starts on the explicitly declared second page. For flowing/automatically paginated chapters, derive the destination pages from a first renderDocumentWithLayout() pass, then render the contents labels in a second pass. Keep the contents page's space/page count fixed between passes, or recheck pagination after inserting it. {{pageNumber}} on a TOC entry means the page containing that entry, not the destination chapter's page.

Use unique bookmark names and match them exactly: the current writer chooses the first matching title and silently skips an internal link if no matching bookmark exists. See the internal-link implementation and layout/render API. This is the supported building block for a custom TOC, rather than a claim that a ready-made auto-TOC component exists.