fix: resolve TypeScript error in PDFDownloadLink component react-pdf v4

[islam-kamel]

Fixed #2886

Changes Made:

• Updated PDFDownloadLinkProps to correctly handle the 'children' prop, allowing for both ReactNode and function types.
• Ensured compatibility with TypeScript type definitions to prevent type mismatches.
• Added necessary type assertions to preserve functionality.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4a1bdcc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[robbycarter]

Anything i can do to help speed up this PR?

[mamlzy]

@diegomura sorry for tagging you

[fatihgnc]

I need this PR to be merged...

[fabww]

This is still an issue in V4.1.5, is there any fix or workaround for this?

[mamlzy]

This is still an issue in V4.1.5, is there any fix or workaround for this?

yes i still facing this issue. still using @ts-expect-error to ignoring the type errors

[diegomura]

There's an open question in this PR I left on code

[goldenaca]

OKAY

[mouchegmouradian]

when will this be merged ?

[Maquinours]

Up.
It is a big issue for all typescript users.

[robbycarter]

I hope we get this resolved before the end of the year.

[mouchegmouradian]

@robbycarter @Maquinours

Until it's fixed you can do something like this:

the @ts-expect-error is better than @ts-ignore because when this PR is merged and the error isn't there anymore the @ts-expect-error will throw an error itself saying there are no errors, then you can remove it from your code safely.