Is this valid javascript? It does not error, and appears to work.
export {default as Chooser} from "./chooser";
My interpretation is:
importthedefaultfrom"./chooser"exportthe result from #1as Chooser
Is this what is happening?
-
1If it works, what's the question?user663031– user6630312016-09-09 05:57:35 +00:00Commented Sep 9, 2016 at 5:57
-
YesBergi– Bergi2016-09-09 12:56:04 +00:00Commented Sep 9, 2016 at 12:56
Add a comment
|
2 Answers
Your interpretation is correct.
importthedefaultfrom"./chooser"
This is correct. The default thing being exported is Chooser and on import, you must use the name given to it with as ...:
import { Chooser } from "./chooser";
exportthe result from #1 asChooser
This is also correct. The name Chooser is giving the default a new name and exporting it.
Let me break this down:
export {
default as Chooser
} from "./chooser";
What this does is specify the file from which it is exported, and default as Chooser exports the default under the name Chooser. Now, on import:
import { Chooser } from "./chooser";
You must specify Chooser to import because you've essentially named the default.
4 Comments
Really? This is also correct, but the module exports Chooser as default, and then on import, import finds the default export and imports it. I think the module exports it under the name
Chooser, and it must be imported as import {Chooser} from './exports';. If you want to re-export the default export, I think you need to say export {default} from './chooser;. Also, what does foo` in your answer refer to?
Felix Kling
"can be used globally as its the default thing being exported" What does default exports have to do with "globally"? What does that mean in that context?
Andrew Li
@FelixKling I'm not sure why I put that in but it's removed. Thank you for pointing that out!
Andrew Li
@torazaburo I have edited the answer, thanks for the constructive criticism!