Skip to content
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

Allow each Component to be imported from respective root folder: multi-entry support #425

Closed
andreawyss opened this issue Jan 10, 2020 · 6 comments · May be fixed by #367
Closed

Allow each Component to be imported from respective root folder: multi-entry support #425

andreawyss opened this issue Jan 10, 2020 · 6 comments · May be fixed by #367
Labels
solution: duplicate This issue or pull request already exists topic: multi-entry Related to multi-entry support

Comments

@andreawyss
Copy link

Sorry for the question, but I could not find info in the docs on how to do this.

I have a library of React Components with a source structure similar to:
https://github.com/mui-org/material-ui/tree/master/packages/material-ui/src

Is it possible to setup TSDX to build the library so that one can import individual components from their individual root folders?

   import Avatar from 'my-library/Avatar';
   import Button from 'my-library/Button';

Currently using TSDX we are forced to import all the components from the root index

   import { Avatar, Button } from 'my-library';

Thank you.

@ambroseus
Copy link
Contributor

@andreawyss you are not alone)
#175 (comment)

@ambroseus
Copy link
Contributor

ambroseus commented Jan 11, 2020

@ambroseus

This comment has been minimized.

@brainkim

This comment has been minimized.

@ambroseus

This comment has been minimized.

@agilgur5
Copy link
Collaborator

Related to or duplicate of #365, #367, #175 , #276 , #299, #321

@agilgur5 agilgur5 changed the title Allow each Component to be imported from respective root folder Allow each Component to be imported from respective root folder: multi-entry support Mar 9, 2020
@agilgur5 agilgur5 added the solution: duplicate This issue or pull request already exists label Mar 9, 2020
@agilgur5 agilgur5 closed this as completed Mar 9, 2020
@agilgur5 agilgur5 added the topic: multi-entry Related to multi-entry support label Mar 10, 2020
@agilgur5 agilgur5 added kind: feature New feature or request and removed kind: feature New feature or request labels Jul 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solution: duplicate This issue or pull request already exists topic: multi-entry Related to multi-entry support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants