-
Notifications
You must be signed in to change notification settings - Fork 509
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
Example with importing from published subdirectories: multi-entry support #299
Comments
its fine, not bad practice. i’m just not sure we support it tbh. |
According to this it is possible if you pass a json object as input. Will try it now. |
Doesn't seem so... |
I used TSDX to make a lib for my commonly used hooks, mixins, React components, utils here: I’d like to be able to import from apostrof/hooks, apostrof/mixins, and so on. But it looks like I can’t use TSDX for this use case? What other option do I have? |
Rollup support that. TSDX uses it under the hood. |
When I run yarn build, it generates empty bundles. Am I missing something in package.json? |
This is the same issue as #276. Bundling libraries is ultimately a leftover from before automated dependency management or having an automated build step was the norm. A significant downside is that bundled sub-dependencies don't get deduplicated. It's a fairly large oversight in tsdx. |
I will close it now. Moving discussion to #276 |
I want to be able to do this:
Is this a bad practice? If not, can we have an example of how to do it in the docs?
The text was updated successfully, but these errors were encountered: