BUG: "export 'default' (imported as 'selection_enter') was not found in './enter'

[kukjevov]

Do you want to request a feature or report a bug?
BUG

What is the current behavior?
Currently if you try to use d3.js library, webpack will generate warning:
"export 'default' (imported as 'selection_enter') was not found in './enter'

That is not so big problem, but when you run javascript generated by webpack it will fail with error:
SyntaxError: function statement requires a name

Problem is using ES2015 import default and export default which is not working.

If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/kukjevov/webpack-error-sample

What is the expected behavior?
It should work

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
nodejs: 7.10, webpack 2.5.0, Windows 10

[sokra]

You testcase compiles fine for me... ?

[kukjevov]

As i wrote down it compiles with warnings. But these warnings ends up in browser with syntax error as mentioned above:
SyntaxError: function statement requires a name

Thanks :)

[9still]

had a similar issue, but realized it was caused by module (d3-shape) being written in ES6 & being excluded from babel-loader in my config, fixing that got rid of the warning - possible you have a similar issue @kukjevov ?

[kukjevov]

Well i have temporarily solved it by using import {} from 'd3' as whole library. There is no problem, but with partial 'd3-shape' etc it is not working. But it was working in older versions of Webpack. So this is not critical for me, but i was thinking maybe it is good to look at that if it can cause problems.

Thanks :)

[morlay]

Have the same issue.
Node 7.10 Webpack 2.5.1
With "d3-shape"

4:9-18 "export 'default' (imported as 'ascending') was not found in './ascending'

maybe it is because of the unamed function

# d3-shape/src/constant.js
export default function(x) {
  return function constant() {
    return x;
  };
}

will pack to

/******/ ([
/* 0 */
/***/ (function(module, __webpack_exports__, __webpack_require__) {
"use strict";
function(x) {
  return function constant() {
    return x;
  };
}
/***/ }),
/* 1 */

the export default is missing.
when i named it, it works well.

[morlay]

Sorry, it may be registry mirror issue, use install from npm registry work well, but use https://registry.npm.taobao.org will got this issue.

[scottbedard]

I am experiencing this issue as well with 2.6.1

[frenzzy]

I had the same issue, but it was because I used multi compiler mode (webpack.config.js returns array of configs) and also:

1. For one of compilers the same module did not contain the default export, for example:

   // moduleName/package.json
   {
     "main": "./server.js",
     "browser": "./browser.js"
     // ...
   }
   
   // moduleName/server.js
   export default 'example'
   
   // moduleName/browser.js
   // no default export here

2. The resolve configuration object had shared between multiple configs, like so:

   // webpack.config.js
   const resolve = {};
   
   module.exports = [
     {
       target: 'web',
       resolve: resolve,
       // ...
     },
     {
       target: 'node',
       resolve: resolve,
       // ...
     },
   ];

FYI @sokra
Maybe webpack should not mutate resolve section of config?

[pksjce]

@kukjevov - Your test error repo compiles and shows "Hello World, 4" as I tried it with webpack 3.1. Don't see any warnings. Can you confirm too?

[marvinhagemeister]

I just stumbled upon the same error at work with react:

WARNING in ./components/Button/index.js
56:2-7 "export 'default' (imported as 'React') was not found in '../../..'

Haven't managed to narrow it down to a small test case yet, though.

EDIT: Found the issue!!

In my case the issue was caused by the src/ folder which is react/ in our case (not my project). Something like this:

/myproject
  /react
    Foo.js
    index.js

In this case when importing react import React from "react" the path was resolved to my weirdly named src folder which obviously is not a valid js module.

[luixo]

Got the same problem!
export 'compose' was not found in 'redux'
The issue was that one of my folders in project was named redux.

[xierenyuan]

@morlay 我使用淘宝镜像以遇到这个问题呢。 你更换了源好呢吗?

[nerdess]

this might be of use for someone. had a similar issue when i was updating an old create-react-app application. had to change all occurrences of

module.exports = Blabla;

to

export default Blabla;

[zebulonj]

In case anyone stumbles across this thread... you'll also see the error reported here if you try to process the babel-runtime itself through babel-plugin-transform-runtime (i.e., by not excluding it from the babel-loader in webpack).