Is re-exporting modules harmful for tree-shaking? : <p>I've come into an argument with my co-workers for which we can't seem to find an answer from any official source (MDN, webpack documentation, ...). My research <a href="https://stackoverflow.com/questions/38077164/es6-export-from-import">hasn't yielded much</a> either. There seems to be doubt <a href="https://stackoverflow.com/questions/42051588/wildcard-or-asterisk-vs-named-or-selective-import-es6-javascript">even when it comes to importing</a> as well.</p>

<p>Our setup is Webpack, Babel, and a typical React / Redux app. Take this example:</p>

<pre class="lang-js prettyprint-override"><code>export * from './actions';
export * from './selectors';
export * from './reducer';

export { default } from './reducer';
</code></pre>

<p>This allows me to separate a Redux module into logical sections, making the code easier to read and maintain.</p>

<p>However, it is believed by some of my co-workers that <code>export * from</code> may, in fact, harm <code>webpack</code>'s tree-shaking capabilities, by tricking it into believing an export is used when it is in fact just being re-exported.</p>

<p>So my question is, are there any facts proving or disproving this?</p>
