-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to create index of named exports? #11
Comments
I don't think this belongs in the core, but I will leave the issue open in case anyone else has a similar use case and can propose an implementation. |
Thanks for reply. |
Same question. I'd like to have a simple plain file with all components from nested dirs. |
I have the same issue. The index.js generated for a directory exports the default export of each file, but not not in itself export a default export. In this case, how can a parent directory re-export the default export of the child directory? I updated it to work in this situation here although I was getting errors when using this syntax: export * as queen from './queen'; and instead use this syntax: import * as queen from './queen';
export { queen }; |
@deadivan Can you enable issues in your fork? |
I use webpack and babel as my es6 transpiler in my dev.create-index act correct when all siblings are files. It breaks when export subdir.
For example
create-index can correctly build index.js in dir queen
but in the root dir ,index.js
just export
undefined
.I found that
worked.
So I forked your code and change the dir export style and committed.
https://github.com/deadivan/create-index
Please tell me if I doing something wrong.
The text was updated successfully, but these errors were encountered: