-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Feature Request: Export a helper function that lists all the internal packages #104
Comments
What happens if you don't list the packages? I am using I see no reason to bundle them with your js output. It seems you would then deploy the packages code twice. |
Without using
I am using the internal packages strategy without a build step for the packages, so maybe that could be the difference between both of our outcomes. When I use |
Ah yes that makes sense! I think it's a good suggestion. It should be easy to add, but I'm not sure when I'll get to it. Feel free to submit a PR ;) |
It would be great if you could provide a function that returned all the internal package names as a string array.
This would make integrating
isolate-package
andtsup
much simpler.At the moment we have to manually list all of the internal packages in the tsup
noExternal
config property. But sometimes I forget to do that and I see strange errors that are hard to track down until I remember to add any new internal packages to thenoExternal
list.I assume
isolate-package
has a way of identifying the internal packages, so if you could export that as a helper function for us we could easily use it within tsup to solve this issue.This is how my current tsup.config.ts file looks. I have to manually list all the internal packages. This is error prone because I often forget to list them here.
This is how is could it work if you exported a helper function for us. The internal packages are automatically listed using an
isolate-package
helper function namedinternalPackages
(just a name suggestion).The text was updated successfully, but these errors were encountered: