bug: Preact typing doesn't work if using non-legacy TypeScript moduleResolution

[maxpatiiuk]

bug: Preact typing doesn't work if using non-legacy TypeScript moduleResolution

[maxpatiiuk]

As per preactjs/preact#1180 (comment), changing the preact.d.ts that Calcite generates like so appears to work both with the legacy and the new moduleResolution strategy:

- import { JSXInternal } from "preact/src/jsx"; 
- import { JSX } from "./components";
+ import { JSX as JSXInternal } from "preact";
+ import { JSX as CalciteJsx } from "./components";

- declare module "preact/src/jsx" {
-   namespace JSXInternal {
+ declare module 'preact' {
+   namespace createElement.JSX extends JSXInternal.IntrinsicElements {

This seems to work because new versions of TypeScript look at the jsx factory function to resolve the JSX namespace

In addition:

• Rename usages of JSX.Calcite* in the file with CalciteJsx.Calcite*)
• Duplicate the contents of namespace createElement.JSX extends JSXInternal.IntrinsicElements { ... } and call it namespace h.JSX extends JSXInternal.IntrinsicElements { ... } so that typing works both for people using "jsxFactory": "h" and "jsxFactory": "createElement"`

@paulcpederson Since you worked on the original Calcite types for Preact, could you please verify if the above fix looks good and if so if it can be integrated into the preact.d.ts that Calcite ships?