Default export not found when exporting as object literal

[santiagoaguiar]

I'm using the following syntax:

export { 
    foo as default,
    bar
}

And later importing as:

import foo, { bar } from "foo";

But I'm getting a 'No default export found in module'. Code runs and compiles fine with babel.

Switching the foo module to:

export const bar = ..;
export default foo;

Works OK.

Using 0.8.0, with babel-eslint 1.4.3 as parser.

[benmosher]

Fascinating. I have never run into this syntax. Esprima is cool with it too.

I would have thought this was invalid, but given the spec on exports, seems like this is a normal case. Not without precedent, either.

I'm not totally clear on whether this is valid per the spec (Babel allows a lot of things), but it certainly seems useful.

I'm not sure what to do... seems like the pragmatic thing is to handle it as you've described.

[benmosher]

Probing the net with this StackOverflow post, too.

[santiagoaguiar]

I think it should be accepted according to http://www.ecma-international.org/ecma-262/6.0/#table-42.

[benmosher]

Yeah, between that and table 40, I think you're right. I will handle. 😁👍

[benmosher]

Let me vet the changes a little tomorrow at work, and then I will publish as 0.8.1. Thanks for the report!

[santiagoaguiar]

Amazing!! Thanks a lot for that prompt reply :).

I used the new version and it worked great for me.