<p dir="auto">Followup from a tweet from Unpkg (unpkg?) about ES6 module support:<br>
<a href="https://twitter.com/unpkg/status/905239560988221440" rel="nofollow">https://twitter.com/unpkg/status/905239560988221440</a></p>
<blockquote>
<p dir="auto">For fun, try using <code class="notranslate">import * as d3 from '//unpkg.com/d3?module</code> inside a &lt;script type=module&gt; and watch those modules load!</p>
</blockquote>
<p dir="auto">It would be neat if you could just <code class="notranslate">import { Component }  from 'https://unpkg.com/react?module'</code> in browsers like Safari (and soon Chrome). As far as I understand the problem, we'd just need to export an ES6 build target from Rollup.</p>
<p dir="auto">I use "just" lightly. Hopefully it's that simple; it's probably more complicated. In any case, now we have an issue for it!</p>
<p dir="auto"><strong>Do you want to request a <em>feature</em> or report a <em>bug</em>?</strong><br>
Request a feature</p>
<p dir="auto"><strong>What is the current behavior?</strong><br>
React ecosystem was promoting ES6 classes and modules since 2014 and many packages like react-router, redux and so on, have an "es" folder in the npm package with source code in ES2015 modules. Unless I am missing something, it is strange that React itself does not offer that option.</p>
<p dir="auto"><strong>If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via <a href="https://jsfiddle.net" rel="nofollow">https://jsfiddle.net</a> or similar (template: <a href="https://jsfiddle.net/84v837e9/" rel="nofollow">https://jsfiddle.net/84v837e9/</a>).</strong><br>
Install react and try to import it in a browser with native modules enabled.</p>
<p dir="auto"><strong>What is the expected behavior?</strong><br>
Have an "es" folder in the npm package with ES2015 modules source code, like most React ecosystem projects do. Allow to import react from ES2015 native modules to make developer workflow more simple.</p>
<p dir="auto"><strong>Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?</strong><br>
All versions</p>