javascript import from '/folder' with index.js : <p>I've noticed a few cases where I've seen something like the following:</p>

<p><div class="snippet" data-lang="js" data-hide="false">
<div class="snippet-code">
<pre class="snippet-code-js lang-js prettyprint-override"><code>// /reducers/reducer1.js
export default function reducer1(state = {}, action){
  // etc...
}
  
// /reducers/reducer2.js
export default function reducer2(state = {}, action){
  // etc...
}

// /reducers/index.js
import { combineReducers } from 'redux';
import reducer1 from './reducer1';
import reducer2 from './reducer2';

export default combineReducers({
  reducer1,
  reducer2
})
  
// /store.js
import masterReducer from './reducers';

export default function makeStore(){
  // etc...
}</code></pre>
</div>
</div>
</p>

<p>Notice the last "file" where we call <code>import masterReducer from './reducers'</code> - A few people seem to believe this should import the <code>default export</code> from the index.js file.</p>

<p>Is this actually part of the specification? - my interpretation/question is that this is the result of many folks using WebPack v1 which translates <code>import</code> statements into CommonJS-style <code>requires</code> statements? Or will this break in WebPack v2 with "official" <code>import</code>/<code>export</code> support?</p>
