I didn't find out anything related to issues with shebang using react.
So it is not common unless is a new problem, but I doubt that.
What I found is a similar error but with ts-loader reference.
I don't know if this is going to work as the #61 does not occur on my console, just on bundlephobia. (or was hidden among the conflict errors).(which is clean now)
But makes sense cause as it is not recognizing JSX syntax.
[x] And this resolved sucessfully react-native conflict with dom types. answer
I didn't find out anything related to issues with shebang using react. So it is not common unless is a new problem, but I doubt that.
What I found is a similar error but with ts-loader reference. I don't know if this is going to work as the #61 does not occur on my console, just on bundlephobia. (or was hidden among the conflict errors).(which is clean now) But makes sense cause as it is not recognizing JSX syntax.