Repository navigation
Forward flutter packages commands to pub #9799
Description
Activity
- added this to the milestone
on May 4, 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.
- modified the milestones: ,
on May 5, 2017 OK, we can do that.
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.- locked as resolved and limited conversation to collaborators
on Aug 30, 2021
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 packagescommands. At least the following seem to make sense:Already supported
flutter packages get->pub getflutter packages upgrade->pub upgradeShould 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 commandsCan be ignored
pub build: web workflow, not relevantpub serve: web workflow, not relevantpub help: flutter has it's own help