The problem here is that the version of React your project is using (^18.2.0) is not compatible with the react-to-pdf package's definition, which requires react version ^16.5.2 to be installed. At first glance, this may seem like an invalid error: the package expects a version higher than 16.5.2, and you've installed something above 18.2.0. However, any major version bump will create an incompatible state. We can understand this explicitly by reading npm's documentation on this topic, which states the following:

Assuming the host complies with semver, only changes in the host package's major version will break your plugin. Thus, if you've worked with every 1.x version of the host package, use "^1.0" or "1.x" to express this. If you depend on features introduced in 1.5.2, use "^1.5.2".

Armed with all of that knowledge, we now have handful of options for resolving this issue:

1. Force install the plugin or use the legacy peer dependencies option, either of which provides no guarantee that this package works with your version of react.
2. Downgrade react (this is technically an option, but don't do it).
3. Find a more up-to-date alternative that accomplishes the same goal and is compatible with your version of react.

Additionally, if you really like this package, I would recommend opening up an issue on the maintainer's repository to ask for an update that tests compatibility with newer versions and publishes a new version of their own package.

Finally, I would recommend becoming familiar with this kind of error message and read through some of the official documentation on npm's website because this kind of thing is fairly common and understanding the basics will save you many future headaches.