/* @jsxRuntime automatic *//* @jsxRuntime automatic */ comment to a file has the same effect as setting compilerOptions.jsxcompilerOptions.jsx to "react-jsx""react-jsx" for that file, but this doesn't seem to be the case. I have a main.tsxmain.tsx file with the following content.deno check main.tsxdeno check main.tsx reports an error: “JSX element type '<>' does not have any construct or call signatures”, but if I create a deno.jsondeno.json file with compilerOptions.jsxcompilerOptions.jsx set (which I expected to do nothing because there's already a @jsxRuntime@jsxRuntime pragma), the error goes away.Join the Discord to continue the conversation