title: es6 Import of three.js
body: <p>My workflow for es6 uses babel and babel-plugin-transform-es2015-modules-system.js to <em>only</em> transform module import/export for use with system.js. I simply use a "green" browser for all es6 features except import/export of modules .. which are a whatwg standard thus not "es6".</p>
  
  <p>This works with legacy (non-es6) libraries well, I can "import" all the npm packages I need. Somehow babel, with only the babel modules transform, and system.js magically work.</p>
  
  <p>Except for three.js.  I tried it with all three releases: three.js, three.min.js &amp; three.modules.js. The first two fail silently, resulting in a "undefined" module. The third fails, wanting traceur .. I guess for a system.js-like transform?</p>
  
  <p>So what do I need to do to use three.js in my es6 world?</p>
  
  <p>I guess I could just use a <code>&lt;script&gt;</code> tag and a global for three. Or possibly use rollup/webpack to eliminate the modules?</p>
  
  <p>But I bet there's a reasonable solution. After all, three.js uses es6 modules internally.</p>