'React' refers to a UMD global, but the current file is a module. Consider adding an import instead.

[danikane]

Hi,
JavaScript and TypeScript Nightly version 5.7.20240928 and subsequent versions report the above message.

Next.js 13 or 14, pages router
Windows 10 with WSL2
VSCode 1.93.1

This is a React Fragment and there are several workarounds, but none of them are desired:

• import React obviously
• change "jsx": "preserve" -> to "jsx": "react-jsx" in tsconfig.json in which case Next will slap you
  
• change to div or whatever :)

On a side note ESLint doesn't pick it up when linting, but then again it's misleading.
Thanks!

[iisaduan]

@danikane does this only happen when the config is set to jsx: preserve? Can you install and try #60122 (comment)?

[danikane]

Yes, exactly. That's what Next.js automatically sets anyway.
I can try tomorrow and get back with the results, if that's ok with you.
Thanks!

[danikane]

By the way should I leave the latest nightly installed?

[iisaduan]

If you npm install the dev version I linked, it will remove the nightly version and install the dev version in its place. You can either reference it in your dev dependencies and then run npm install, or use npm install typescript@npm:@typescript-deploys/pr-build@5.7.0-pr-60122-2 (regardless of what is in your dependencies) to try it out.

[iisaduan]

@danikane I've made changes to that PR that shouldn't affect typechecking, but I've packed a new version just in case: #60122 (comment)
"typescript": "npm:@typescript-deploys/pr-build@5.7.0-pr-60122-16"

[danikane]

@iisaduan Thank you, I confirm the error is no longer reported!

[iisaduan]

Great, thank you for confirming!

[imranbarbhuiya]

Seems like it's happening in stable release too using "jsx": "react-native",

[imranbarbhuiya]

Hi @iisaduan, sorry for the ping but should i create a new issue for it or this can fixed from this issue only?

[ChromeQ]

Seems like it's happening in stable release too using "jsx": "react-native",

Same thing here