You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Flutter and Dart CLIs offer an option to turn off calling pub get before they run, which slows them down.
It's called --no-pub, and can be passed to analyze, test (although Melos doesn't have a test command), etc.
Reasoning
I'm on a rather limited machine, so reducing redundant work is important. pub get can take up to a minute, and while pub workspaces will unify most stuff, they'll also (probably) slow down pub get even more.
Additional context and comments
Alternatively, passing unknown flags to the underlying command might work as well.
The text was updated successfully, but these errors were encountered:
Makes sense, would you be interested in working on that issue?
Interested, yes; actually do it, probably someday? 😁 Now that I think about it, it'd probably be a good introduction before I tackle #747 (I plan on getting to that if no one else does, but I'm pretty busy with other obligations at the moment). (Oh, you're doing that in #816. Thanks!)
Is there an existing feature request for this?
Command
No response
Description
The Flutter and Dart CLIs offer an option to turn off calling
pub get
before they run, which slows them down.It's called
--no-pub
, and can be passed to analyze, test (although Melos doesn't have a test command), etc.Reasoning
I'm on a rather limited machine, so reducing redundant work is important.
pub get
can take up to a minute, and while pub workspaces will unify most stuff, they'll also (probably) slow downpub get
even more.Additional context and comments
Alternatively, passing unknown flags to the underlying command might work as well.
The text was updated successfully, but these errors were encountered: