amplify-prompts
amplify-prompts
npm i amplify-prompts
amplify-prompts

amplify-prompts

The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.

by aws-amplify

2.2.0 (see all)License:Apache-2.0TypeScript:Not Found
npm i amplify-prompts
Readme
AWS Amplify

Discord Chat build:started

Reporting Bugs/Feature Requests

Open Bugs Feature Requests Enhancements Closed Issues

AWS Amplify CLI

The AWS Amplify CLI is a toolchain which includes a robust feature set for simplifying mobile and web application development. The CLI uses AWS CloudFormation and nested stacks to allow you to add or modify configurations locally before you push them for execution in your account.

Install the CLI

  • Requires Node.js® version 12 or later

Install and configure the Amplify CLI as follows:

$ npm install -g @aws-amplify/cli
$ amplify configure

Note: If you're having permission issues on your system installing the CLI, please try the following command:

$ sudo npm install -g @aws-amplify/cli --unsafe-perm=true
$ amplify configure

Commands Summary

The Amplify CLI supports the commands shown in the following table.

CommandDescription
amplify configureConfigures the AWS access credentials, AWS Region and sets up a new AWS User Profile
amplify initInitializes a new project, sets up deployment resources in the cloud and prepares your project for Amplify.
amplify configure projectUpdates configuration settings used to setup the project during the init step.
amplify add <category>Adds cloud features to your app.
amplify update <category>Updates existing cloud features in your app.
amplify push [--no-gql-override]Provisions cloud resources with the latest local developments. The 'no-gql-override' flag does not automatically compile your annotated GraphQL schema and will override your local AppSync resolvers and templates.
amplify pullFetch upstream backend environment definition changes from the cloud and updates the local environment to match that definition.
amplify publishRuns amplify push, publishes a static assets to Amazon S3 and Amazon CloudFront (*hosting category is required).
amplify status [ <category>...]Displays the state of local resources that haven't been pushed to the cloud (Create/Update/Delete).
amplify status -v [ <category>...]Verbose mode - Shows the detailed verbose diff between local and deployed resources, including cloudformation-diff
amplify serveRuns amplify push, and then executes the project's start command to test run the client-side application.
amplify deleteDeletes resources tied to the project.
amplify help | amplify <category> helpDisplays help for the core CLI.
amplify codegen add | generatePerforms generation of strongly typed objects using a GraphQL schema.
amplify env add | list | remove | get | pull | import | checkoutSee the multienv docs.

Category specific commands:

Tutorials

Developing

To set up your local development environment, go to Local Environment Setup.

To test your category, do the following:

cd <your-test-front-end-project>
amplify-dev init
amplify-dev <your-category> <subcommand>

Before pushing code or sending a pull request, do the following:

  • At the command line, run yarn lint at the top-level directory. This invokes eslint to check for lint errors in all of our packages.
  • You can use yarn lint to find some of the lint errors. To attempt fix them, go to the package that has errors and run yarn lint-fix
  • If there are any remaining lint errors, resolve them manually. Linting your code is a best practice that ensures good code quality so it's important that you don't skip this step.

Contributing

We are thankful for any contributions from the community. Look at our Contribution Guidelines.

Downloads/wk

58.1K

GitHub Stars

2.6K

LAST COMMIT

5mos ago

MAINTAINERS

1

CONTRIBUTORS

253

OPEN ISSUES

565

OPEN PRs

57
VersionTagPublished
2.2.0
latest
3mos ago
2.3.0-rc.224a2e0e4.0
rc
4d ago
2.3.0-pretty-print.1
pretty-print
13d ago
2.2.1-alpha.55
canary
1mo ago
No alternatives found
No tutorials found
Add a tutorial