<p dir="auto">Simply trying to add <code class="notranslate">OrbitControls</code> to <code class="notranslate">three.min.js</code> by following the instructions in the Wiki. Working from a fresh clone of the master branch of r120 on a Windows 10 machine with current Node and npm. Added the line</p>
<p dir="auto"><code class="notranslate">export { OrbitControls } from '../examples/jsm/controls/OrbitControls.js';</code></p>
<p dir="auto">to <code class="notranslate">src/Three.js</code> and ran <code class="notranslate">npm install</code> followed by <code class="notranslate">npm run build-closure</code>. The resulting file is twice as big as expected, and further runs of the build keep increasing file sizes. Either something critical is missing from the Wiki instructions or there is an error somewhere.</p>
<p dir="auto">Ricardo, why did you delete the reported issue?<br>
I'm a 3DS Max user since the DOS era, so I know very well what I'm saying.<br>
Again:</p>
<ul dir="auto">
<li>import an object (OBJ, DAE, whatever) with many childrens.</li>
<li>perform some scale/rotation/position changes on the imported object (all the childrens will be afected).</li>
<li>detach one children (the mesh)</li>
<li>create a new GROUP</li>
<li>attach that mesh to the group.</li>
</ul>
<p dir="auto">Result: everything is messed up !<br>
That previous child object will get position and rotation (0,0,0) and scale(1,1,1).<br>
And that's wrong!<br>
Perform the same operations with 3DS Max.<br>
The new group (parent) will not mess up the new children parameters.</p>
<p dir="auto">cheers</p>