Combination of
Flutter+Simplify
Instead of copy pasting scripts for every new flutter project I'm working on I can just run
fon a flutter project and run these common daily tasks.
f clean
# => Deep cleans the project and rebuilds it.
f fix
# => Automatically identifies and corrects common issues in Dart code, such as outdated syntax.
f fix
# => Automatically identifies and corrects common issues in Dart code, such as outdated syntax
f bump major|minor|patch|build
# => bumps the corresponding update type (and it always bumps the build number)
f generate swagger|icon|assets
# => swagger: Executes a function to generate a Swagger (OpenAPI) client.
# => icon: Generates the icons for the app. (using "flutter_launcher_icons")
# => assets: Initiates asset generation and management. (using "fluttergen")
f open ios|android
# => ios: Opens the appstoreconnect website.
# => android: Opens the play console website.
f release beta|production
# => beta: Releases the current build to the beta track.
# => production: the current build to the production track.
Clone the repo in your designated folder
git clone git@github.com:cesarferreira/flutterfy-cli.git
Now add to your ~/.bashrc or ~/.zshrc
alias f="ruby -Ilib PATH_TO_GEM_FOLDER/f/bin/f"
flutter pub run build_runner watch -dFAQs
Unknown package
We found that flutterfy-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.