Switch to ForwardRefExoticComponent for Preact compatibility

[8Crafter]

The type React.NamedExoticComponent does not exist, but React.ElementType does exist and works exactly how it needs to for what that non-existent type is being used for.
This is a necessary fix to fix the autocompletion of properties for the react components.

[8Crafter]

To anyone seeing this who is not a maintainer of this project, if this still hasn't been merged when you see this, then you can use this type declaration as a temporary fix until it is merged:

declare global {
    namespace React {
        /**
         * An alias for {@link React.ElementType | React.ElementType\<P\>} to fix the component types of {@link https://www.npmjs.com/package/@szhsin/react-menu | @szhsin/react-menu}.
         */
        export type NamedExoticComponent<P = any> = React.ElementType<P>;
    }
}

[szhsin]

Did you have @types/react installed in your project? React.NamedExoticComponent has been around since React 16 and is still included in @types/react up through the latest v19. I’m not seeing an issue here.

[szhsin]

@Andexter8 Since you also raised #1591, I assume this PR is related to using the package with Preact, which explains why NamedExoticComponent does not exist. It looks like the typings in preact/compat only include ForwardRefExoticComponent.

A proper fix to the issue is likely to replace all instances of React.NamedExoticComponent with React.ForwardRefExoticComponent. This ensures the types are supported in both React and Preact.

If that resolves the issue, please update your PR with the change.

[8Crafter]

I will try that tomorrow.

[szhsin]

@8Crafter since I haven’t heard back from you, I’ve updated the PR as previously discussed