-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Only require tty-...
gems that are used in the app
#70
Comments
💯 agree, The short term plan is to inject tty dependencies as comments in the gemspec file for user to pick and choose. This is currently implemented in the The long term plan is to use This comment I made in the referenced issue above explains the 3 stage plan of where I think I want to go with this project. So in the first stage, all tty components would be injected as commented out dependencies. It's kind of similar to how Please let me know if you like this approach as a first step? |
Describe the problem
Perhaps more of a feature suggestion than a problem :) I noticed that when making a new app with
teletype
, it adds all of the 'tty' gems as dependencies, even though (by default) none of them are used orrequire
d:This seems inefficient; if I install this gem straight out of the box - no commands added, etc - I'd get 20 other gems along with it, even though none of them are used (seemingly).
Steps to reproduce the problem
ExpectedSuggested behaviourMy initial thoughts were:
a) use the 'teletype' command to add a new component. for example,
teletype require prompt
(???)b) when running
rake build
, scrape anyrequire
s that reference a tty gemOption "b" sounds more automated (yay!) but hacky (boo!). Option "a" feels clunky (i.e. why would i need to run
teletype
instead of just adding arequire 'tty/prompt'
line..?)... so I'm not sure either suggestion is the best. Opening this more for discussion than anything!Describe your environment
The text was updated successfully, but these errors were encountered: