-
Notifications
You must be signed in to change notification settings - Fork 262
Feature: Automatic Install #687
Comments
See existing issues about this. It used to be automatic once. But that just brings up a different set of issues with people asking why global doesn't automatically install when using sub-dependencies. The locations are all pretty straightforward though and documented in the README. Only |
Also, I don't think it will never do the first thing you want. There's a huge difference between a definition that's global vs local. It's possible the global version isn't even for the same thing, just because a name matches it doesn't mean it's the same. |
A good example is probably |
Very good points, here are my thoughts:
|
@fny I don't think you understand. This is all how it worked when I first released it, before I even announced it. It turned out to be not great for various reasons. Also, why would you expect it to install |
Sorry, that wasn't meant to be harsh. Multitasking can be bad. Popular is just subjective. The best one isn't possible to automatically know. Would it be useful to re-add a |
Hi @blakeembrey where do you get definitions from then? Do you write and maintain your own set of typings?
|
It would be lovely to have a flag that would just take care of any installation issues (e.g.
typings install --do-whatever-you-need-to-do-to-install some-module
.) I know this might seem pretty minor, but this back-and-forth has become tiresome:typings install some-module
typings install dt~some-module
typings install dt~some-module --global
The text was updated successfully, but these errors were encountered: