Deno•6mo ago

`@jsxRuntime` pragma

The TSConfig reference claims that adding a

/* @jsxRuntime automatic */

/* @jsxRuntime automatic */

/* @jsxRuntime automatic */

/* @jsxRuntime automatic */ comment to a file has the same effect as setting

compilerOptions.jsx

compilerOptions.jsx

compilerOptions.jsx

compilerOptions.jsx to

"react-jsx"

"react-jsx"

"react-jsx"

"react-jsx" for that file, but this doesn't seem to be the case. I have a

main.tsx

main.tsx

main.tsx

main.tsx file with the following content.

/* @jsxRuntime automatic */
/* @jsxImportSource npm:hastscript@9.0.1 */
console.log(<></>);

/* @jsxRuntime automatic */
/* @jsxImportSource npm:hastscript@9.0.1 */
console.log(<></>);

/* @jsxRuntime automatic */
/* @jsxImportSource npm:hastscript@9.0.1 */
console.log(<></>);

/* @jsxRuntime automatic */
/* @jsxImportSource npm:hastscript@9.0.1 */
console.log(<></>);

Without a config file,

deno check main.tsx

deno check main.tsx

deno check main.tsx

deno check main.tsx reports an error: “JSX element type '<>' does not have any construct or call signatures”, but if I create a

deno.json

deno.json

file with

compilerOptions.jsx

compilerOptions.jsx

compilerOptions.jsx

compilerOptions.jsx set (which I expected to do nothing because there's already a

@jsxRuntime

@jsxRuntime

@jsxRuntime

@jsxRuntime pragma), the error goes away.

{
  "compilerOptions": {
    "jsx": "react-jsx"
  }
}

{
  "compilerOptions": {
    "jsx": "react-jsx"
  }
}

{
  "compilerOptions": {
    "jsx": "react-jsx"
  }
}

{
  "compilerOptions": {
    "jsx": "react-jsx"
  }
}

Am I missing something, and is there a way to suppress this error without having to make a config file or adding a ignore comment?

No replies yetBe the first to reply to this messageJoin