JSX type definition in Preact 8 is moved into preact namespace or JSX type definition is added to global for compatibility

[38elements]

The namespace of JSX was changed.
This is breaking change.
I think that it is better to specify in the release notes.

preact/src/index.d.ts

Lines 6 to 8 in b4e059a

	declare namespace preact {
	export import JSX = JSXInternal;

preact/src/preact.d.ts

Lines 168 to 170 in 3aaa578

	declare global {
	namespace JSX {
	interface Element extends preact.VNode<any> {

To solve the following issue, I think that it is better to add JSX type definition to global.

developit/unistore#158

I think it is better that JSX type definition in global be deprecated.

[ForsakenHarmony]

To solve the following issue, I think that it is better to add JSX type definition to global.

I think it is better that JSX type definition in global be deprecated.

So uhh which one are you asking for?

global was removed because it conflicted with react

[38elements]

So uhh which one are you asking for?

JSX is added to global.
And JSX exists global until Preact 8 support is terminated.

Or JSX in Preact 8 is moved into preact namespace.

[38elements]

I think it is better that JSX type definition in Preact 8 is moved into preact namespace.

[ForsakenHarmony]

Release in v8.5.0

[aMarCruz]

Great, now porting my 8.x preact app to 10 breaks my toolchain because "JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists".

My app uses JavaScript with TS 3.5 only to enable // @ts-check.
Using @types/react fixes this issue but breaks other things, I'm not using preact/compat.

[38elements]

In 8.4.x, JSX exists in global namespace.
In 8.5+, JSX exists in global namespace and preact namespace.
In 10, JSX exists in preact namespace.