You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a problem, VSCode highlights all preact/html elements in red as an error. JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists.
I noticed that if I add these 3 lines to each element, the problem of highlighting the error disappears, but then this creates another problem, this time with compilation.
/** @jsx h *//** @jsxFrag Fragment */import{h,Fragment}from"preact";
Watcher File change detected! Restarting!
error: Uncaught (in promise) TypeError: pragma cannot be set when runtime is automatic at file:///A:/_CODE/SVG_DENO/svg-chart-family/routes/index.tsx:1:1
pragmaFrag cannot be set when runtime is automatic at file:///A:/_CODE/SVG_DENO/svg-chart-family/routes/index.tsx:2:1
const manifest = (await import(toFileUrl(join(dir, "fresh.gen.ts")).href))
^
at async dev (https://deno.land/x/fresh@1.6.8/src/dev/dev_command.ts:38:21)
at async file:///A:/_CODE/SVG_DENO/svg-chart-family/dev.ts:8:1
Watcher Process failed. Restarting on file change...
The text was updated successfully, but these errors were encountered:
j-Cis
changed the title
JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists.
JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists. || pragmaFrag cannot be set when runtime is automatic
Apr 14, 2024
This was a problem for me because I had all my repositories in a shared workspace. As soon as I opened my Deno fresh app in a single vscode workspace the problem went away.
I have a problem, VSCode highlights all preact/html elements in red as an error.
JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists.
I noticed that if I add these 3 lines to each element, the problem of highlighting the error disappears, but then this creates another problem, this time with compilation.
This problem was also noticed in deno: https://github.com/denoland/deno/issues/23339
The text was updated successfully, but these errors were encountered: