Is export {default} from './Component' valid ES6

Question

I ask this because, If I do this in index.js

import Comp from './Component';

export default Comp

Then doing import Component from 'src/Component' WebStorm would not report as error,

but if I do in index.js

export { default } from './Component';

Then doing import Component from 'src/Component' WebStorm will say Component is not found. As far as I know it's valid and the code actually works, but is it part of the standard of ES6 this style of exporting?

Yes, it's valid ES6. If WebStorm doesn't recognise it, it appears to be their fault. — Bergi, Oct 06 '17 at 17:14

Sagiv b.g · Answer 1 · 2017-10-06T17:15:31.100

2

You can do a named export:

export { default as Component } from './Component';

then you would need to import it like that:

import { Component } from './path';

edited Oct 06 '17 at 17:15

answered Oct 06 '17 at 17:06

Sagiv b.g

28,620
8
59
91

1

wouldn't that be a named export? so the `import would be import { Component } from 'src/Component'` – Yichaoz Oct 06 '17 at 17:10
indeed. that is a named export. – Sagiv b.g Oct 06 '17 at 17:11
there is a [proposal](https://github.com/leebyron/ecmascript-more-export-from) of what you are seeking for – Sagiv b.g Oct 06 '17 at 17:13
The proposal is for `export default from`, but `export { default } from` is fine in ES6. – loganfsmyth Oct 06 '17 at 17:37

Is export {default} from './Component' valid ES6

1 Answers1