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
Seems like we trigger a look-up for React in jsx: preserve.
Ideally we wouldn't - everything should be defined in the JSX namespace?
This error in jsx: preserve is useful for people who are using older React, or if the JSX namespace isn't found for some reason.
Why is Next.js not using jsx: react17?
Hi @DanielRosenwasser do you know if there's answers to any of these from your meeting?
Those of us on Next seem to be stuck with the "importing react" issue when using JSX/TSX :(
jsx: preserve
Without Importing React#41762
React.createElement
.allowUmdGlobalAccess
React
injsx: preserve
.jsx: preserve
is useful for people who are using older React, or if the JSX namespace isn't found for some reason.jsx: react17
?.jsx
file whenmodule: node12
andjsx: preserve
😬jsxImportSource
is enabled; don't need to introduce a new flag.React
?React
namespace.jsxImportSource
is enough today.Template Literal Types as Discriminants
#46137
Someone suggested something like this ought to work.
`${string}-bar`
is not comparable with`foo-${string}`
.string
to a"thing" | `foo-${string}`
we used to narrow thestring
to"thing"
as opposed to the whole union.CheckFlags.HasLiteralType
is the magic that lets templates act as discriminants.The text was updated successfully, but these errors were encountered: