This is meant to fix the issue we were having that was causing
errors on our demo deploy. It was exactly the same issue as pointed out on #1432.
This can be seen to be working because the preview deploy of the demo on this PR is
not failing.
The issue was that we were requiring ^18.2.0 on the react-email package, but for
all other packages we were requiring 18.2.0 exactly which meant it would conflict
on the peer dependencies. The solution was making all packages depend on react@^18.2.0.
From NPM's SemVer calculator, this new version resolves to the following currently:
18.2.0
18.3.0
18.3.1
Meaning that if the user chooses to use any of these versions it won't complain about
the peer dependency version.
This PR simply updates the versions of react-email and @react-email/components to their
latest in which these peer dependency versions are fixed.
This is meant to fix the issue we were having that was causing errors on our demo deploy. It was exactly the same issue as pointed out on #1432.
This can be seen to be working because the preview deploy of the demo on this PR is not failing.
The issue was that we were requiring
^18.2.0
on thereact-email
package, but for all other packages we were requiring18.2.0
exactly which meant it would conflict on the peer dependencies. The solution was making all packages depend onreact@^18.2.0
.From NPM's SemVer calculator, this new version resolves to the following currently:
18.2.0
18.3.0
18.3.1
Meaning that if the user chooses to use any of these versions it won't complain about the peer dependency version.
This PR simply updates the versions of
react-email
and@react-email/components
to their latest in which these peer dependency versions are fixed.