Repository navigation
Forward flutter packages commands to pub #9799
Description
Currently we don't support publishing packages/plugins (i.e. pub publish), or running executables from packages (i.e. pub run, for example for package:intl) with the flutter command.
It would be great if we could forward all relevant pub subcommands to equivalent flutter packages commands. At least the following seem to make sense:
Already supported
flutter packages get->pub getflutter packages upgrade->pub upgrade
Should be added
flutter packages downgrade->pub downgrade, the opposite of upgradeflutter packages publish->pub publishto support publishing a pluginflutter packages deps->pub depsto show package dependenciesflutter packages run->pub runto support running executables, e.g. for package:intlflutter packages cache->pub cacheto manage the pub cache contentsflutter packages version->pub versionto see the pub versionflutter packages uploader->pub uploaderto manage package uploadersflutter packages global->pub global: pub global commands
Can be ignored
pub build: web workflow, not relevantpub serve: web workflow, not relevantpub help: flutter has it's own help
Activity
sethladd commentedon May 4, 2017
@mit-mit which of the proposed commands requires the special flutter environment variable to work? I would prioritize those sooner than Milestone 5.
mit-mit commentedon May 5, 2017
I don't think we should do these piecemeal. It should be pretty straightforward to just forward all the listed ones under should be added. I also agree that this should be done earlier than milestone 5; this impacts the flow for publishing plugins.
Hixie commentedon May 31, 2017
I think we should close this as a general bug and track individual commands we feel strongly about independently in their own bugs (e.g. as in #10403).
mit-mit commentedon Jun 1, 2017
OK, we can do that.
github-actions commentedon Aug 30, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.