jsx-runtime | Extremely lightweight JSX runtime to write JSX | Frontend Framework library

Per docs, MUI v5 only supports React v17+:

MUI supports the most recent versions of React, starting with ^17.0.0 (the one with event delegation at the React root). Have a look at the older versions for backward compatibility.

The actual reason why this error shows up is because react/jsx-runtime module only exists in React v17. If you're stuck with v15 or v16 of React, you can update react and react-dom to the latest minor version to fix the error.

Update both packages to the latest version (17+) to fix it:

Edit props destructuring. I would choose the first variant. Its more readable.

You can just simply install in your project by using yarn add typescript @types/node @types/react @types/react-dom @types/jest or npm install --save typescript @types/node @types/react @types/react-dom @types/jest.

If you have a problem with the scripts perhaps updating them will solve it, you can try this command: npm install react-scripts@latest

For further information you can check this links: Create React App and Typescript Docs

Also you may check frameworks that have native support to TS, like Next and Gatsby

The Problem seems to be that you are trying to use Bootstrap which is available for React but not for React Native.

Try to find a different Library that supports your needs like React Native Elements (https://reactnativeelements.com/) or use the Elements that you get from React Native directly.

I would really like to think that the name of the first jsx_runtime would be jsx_runtime_0 and maybe even that if there was only one jsx_runtime then it wasn't suffixed at all by a bundler!

That's no proof, but it made me speculate whether you've actually got two versions of React coming in because each of two modules you include in your project declare it as a dependency (not a peer dependency) and therefore have their own copies which they reference in the bundle.

Since each copy of React uses a different closure to store top-level stuff, this means it notices if e.g. useState is called in the context of a different copy of React.

It looks like you were referring to a dated documentation page. Here is the latest one.

Your should use preact/compat instead:

So my setup actually was working. There was somehow a glitch in the symlink. I as able to resolve by running yarn unlink and yarn link. The package is now bundling correctly.