Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined.

[luokelong]

Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

"@react-pdf/renderer": "^4.0.0", "next": "14.2.13",

"use client";

import { PDFViewer, Document, Page, View, Text } from "@react-pdf/renderer";

const Pdf = () => {
  return (
    <PDFViewer width="100%" height="100%">
      <Document>
        <Page size="A4">
          <View>
            <Text>Hello World!</Text>
          </View>
        </Page>
      </Document>
    </PDFViewer>
  );
};

export default Pdf;

[Tossko]

Same here.

[antonigiske]

I have the same issue using the PDFDownloadLink component.

[luokelong]

Has any official paid attention to this issue?

[lorena-caia]

Same here with "@react-pdf/renderer": "3.4.4", "next": "14.2.12",

[typesafeui]

If anyone is having this issue, there are two temporary fixes:

• Downgrade to next@14.2.8 and to make it work for now
• Put "use client" in the top of the page.tsx file if possible ( not possible if you have any server logic in the page.tsx file )

These are just patches to make it work for now though

[bryanjtc]

The issue is related to a regression in a next.js version or a bug in this package?

[jiri-jirsa]

Same here. Downgrade to next@14.2.8 helped, thanks @typesafeui . Hopefully someone fixes it

[romanslonov]

I also found that importing this way works in "next": "14.2.16":

'use client'

import {Document, Page, View, Text} from "@react-pdf/renderer/lib/react-pdf.browser";