## What was reported

Issue resend/resend-node#124 (closed, 5 comments): Upgraded to the latest version of `@types/react` and a `FunctionalComponent` no longer returns a `ReactElement` which resend expects, instead a `ReactNode` is returned

From the `@types/react` codebase:
## Version 18.0.28
```ts
interface FunctionComponent[P = {}] {
    (props: P, context?: any): ReactElement[any, any] | null;
    propTypes?: WeakValidationMap[P] | undefined;
    contextTypes?: ValidationMap[any] | undefined;
    defaultProps?: Partial[P] | undefined;
    displayName?: string | undefined;
}
```

## Version 18.2.14
```ts
interface FunctionComponent[P = {}] {

## The verified resolution

[jayanratna / vcapretz (maintainers)]: Updating the SDK's React.FC types alone wasn't enough  -  the underlying @react-email render function needed the matching change too. Typing improvements shipped via PR #401; maintainers asked anyone still seeing this on the latest Resend SDK + React versions to reopen. Community workaround: drop the React.FC annotation and declare the email as a plain JSX function.