Sebastian "Sebbie" Silbermann

> In my case, I'm using webpack & babel to build my application. React is excluded from the application bundle and is included from CDN. Is `react/jsx-runtime` also excluded from...

> But it seems a little bit weird to include react/jsx-runtime manually because it's not a required dependency like react and react-dom. `react/jsx-runtime` is just the entrypoint. It is actually...

Yeah it isn't a bundling issue. Sorry for the confusion. The issue is that you're transpiling in development (i.e. `NODE_ENV=production`) but using react's production build from the CDN. These environments...

Generally I don't think you should bundle dependencies assuming different environments. A bundle should only target a single environment not a mix. Some particular combinations "working" is not an argument...

> This was mega frustrating, hope this can help someone else. Thanks to @chulanovskyi and @theKashey for their suggestions as well. @Paddy-Hamilton Always check your lockfile after an install. I...

Thank you for finding this. It's related to `@types/react` and should therefore be opened against https://github.com/DefinitelyTyped/DefinitelyTyped/. Though `name` is not supported in HTML 4 so you should make sure your...

It seems to me that this issue is concerned with two problems: 1. fear of `` not auto-playing because the `muted` attribute isn't set 1. add support of `defaultMuted` React...

> In some browsers (e.g. Chrome 70.0) autoplay doesn't work if no muted attribute is present. Considering Chrome is an evergreen browser and version 70 is over 3 years old,...

> you can't for sure consider it as "not worth it". Sure because that's a subjective statement. But just like we don't work around browser quirks for legacy browsers like...

Which specific node version is causing issues?