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
While starting up my project today, I noticed that my own JSX types dont work anymore (I am not using React). I am using the babel plugin jsx-dom-expressions, which comes with their own JSX typings. However these are now in conflict with @types/react and tsc throws hundredths of errors. Unfortunately, TS is not yet able to exclude a specific dts file. This is related to the changes in #1359. Any chance this change could be reverted so that we can again use react-hot-loader in a project where the JSX is not compiled by React?
Environment
React Hot Loader version: 4.12.16
Run these commands in the project folder and fill in their results:
node -v: v12.13.0
npm -v: 6.12.1
yarn -v: 1.19.1
The text was updated successfully, but these errors were encountered:
Description
While starting up my project today, I noticed that my own JSX types dont work anymore (I am not using React). I am using the babel plugin jsx-dom-expressions, which comes with their own JSX typings. However these are now in conflict with
@types/react
andtsc
throws hundredths of errors. Unfortunately, TS is not yet able to exclude a specific dts file. This is related to the changes in #1359. Any chance this change could be reverted so that we can again use react-hot-loader in a project where the JSX is not compiled by React?Environment
React Hot Loader version: 4.12.16
Run these commands in the project folder and fill in their results:
node -v
: v12.13.0npm -v
: 6.12.1yarn -v
: 1.19.1The text was updated successfully, but these errors were encountered: