Repository navigation
Incorrect/unhelpful error message for non-module jsx file #64438
Description
Activity
The suggestion is valid - but I've also noticed that the Solid docs use
"jsx": "preserve".Under
"jsx": "react-jsx", we automatically force JSX files into module mode. The only way to get something closer to this is by specifying"moduleDetection": "force". That might be something to suggest for their docs if you feel like it's appropriate.Hi Caleb Eggensperger (@calebegg) Daniel Rosenwasser (@DanielRosenwasser) I went through the issue and found that the diagnostic chain needs to be looked up properly. I would like to work on this issue, can you please assign it to me. Thanks!
Hi Caleb Eggensperger (@calebegg) maintainers, I’d like to work on this issue.
I’ve reviewed the reproduction and would like to investigate how the current JSX diagnostic is generated for non-module JSX files. I can work on improving the error message, adding the appropriate regression test, and verifying that the existing behavior for valid module-based JSX remains unchanged.
If this issue is still available, I’d be happy to take it up and submit a PR.
🔎 Search Terms
non-module, script, jsx, jsxImportSource
🕗 Version & Regression Information
⏯ Playground Link
No response
💻 Code
🙁 Actual behavior
🙂 Expected behavior
I do have that package installed. The error message should give the real issue which is that scripts can't import modules.
Additional information about the issue
workaround:
export {}