Shopify CLI commands for apps

Shopify CLI commands should only be run in a project where Shopify CLI is installed.

You can run all Shopify CLI commands using the run command:

You can also run some commands as scripts, which use an abbreviated syntax:

Some package managers require a separator to pass flags to the script:

Builds the app and lets you preview it on a development store or Plus sandbox store.

To preview your app on a development store or Plus sandbox store, Shopify CLI walks you through the following steps. If you've run dev before, then your settings are saved and some of these steps are skipped:

• Associating your project with an app associated with your Partner account or organization, or creating a new app.
• Selecting a development store or Plus sandbox store to use for testing. If you have only one store, then it is selected automatically.
• Installing your app on the store using the provided install link.

• Creating a tunnel between your local environment and the store using ngrok.

  You can use your own tunneling software instead, by passing your tunnel URL with the --tunnel-url flag.

• Updating the app URLs that are set in the Partner Dashboard.

  To avoid overwriting any URLs that are already set, select the No or Never option. If you select one of these options, then you're provided with URLs that you can manually add in the Partner Dashboard so you can preview your app.

• Building and serving your app and app extensions.

If you're using the PHP or Ruby app template, then you need to complete the following steps before you can preview your app for the first time:

• PHP: Set up your Laravel app
• Ruby: Set up your Rails app

You need to create an ngrok account and auth token to preview your app using Shopify CLI.

Displays information about your app.

The information returned includes the following:

• The app and development store or Plus sandbox store that's used when you run the dev command. You can reset these configurations using dev --reset.
• The structure of your app project.
• The access scopes your app has requested.
• System information, including the package manager and version of Shopify CLI used in the project.

Generates a new app extension. For a list of app extension types that you can generate using this command, refer to Supported extension types.

Each new app extension is created in a folder under extensions/. To learn more about the extensions file structure, refer to App structure and the documentation for your extension type.

Generates a GraphQL schema for a function in your app. Run this command from the function directory.

This command uses the API type and version of your function, as defined in your extension TOML file, to generate the latest GraphQL schema. The schema is outputted to stdout.

Builds the app, including extensions.

This command executes the build script specified in the element's TOML file. You can specify a custom script in the file. To learn about configuration files in Shopify apps, refer to App structure.

If you're building a theme app extension, then running the build command runs Theme Check against your extension to ensure that it's valid.

Builds the app and deploys all of the extensions in your app.

If your app contains any versioned app extensions, then you need to navigate to your app in the Partner Dashboard to version and publish the extensions after you run this command.

This command doesn't deploy your web components, such as the code for your embedded app. When you're ready to deploy your app, you need to deploy these components to your own hosting solution, and update the App URLs in the Partner Dashboard to point to your hosted environment. To learn more about deploying your embedded app, refer to Deploy your web app.

The deployment process includes the following steps. If you've run dev or deploy before, then some of these steps are skipped.

• Associating your project with an app associated with your Partner account or organization, or creating a new app.
• Registering any unregistered extensions with the app
• Building the app
• Bundling any app extensions and performing validations on the bundle
• Displaying a confirmation prompt with a summary of the deploy
• Pushing the bundle to Shopify

Creates or updates an .env files that contains app and app extension environment variables.

When an existing .env file is updated, changes to the variables are displayed in the terminal output. Existing variables and commented variables are preserved.

Displays environment variables that can be used to deploy apps and app extensions.

Updates the app URL and allowed redirection URLs for your app. When you specify URLs using this command, the current URLs are overwritten.

Your current app URLs are provided as placeholder responses. To keep either your app URL or redirect URLs the same, submit the placeholder content. Alternatively, use the --app-url or --redirect-urls flag to update only one of these settings.

Enables or disables command autocorrection. By default, autocorrect is off.

When autocorrection is enabled, Shopify CLI automatically runs a corrected version of your command if a correction is available.

When autocorrection is disabled, you need to confirm that you want to run corrections for mistyped commands.

Saves a token to authenticate against ngrok.

ngrok is used to create an HTTP tunnel to your local development environment. You need to create an ngrok account and auth token to use an ngrok tunnel with Shopify CLI. To learn more about creating an auth token, refer to ngrok’s documentation.

Logs you out of the Shopify account or Partner account and store.

Triggers the delivery of a sample Admin API event topic payload to a designated address.

You should use this command to experiment with webhooks, to initially test your webhook configuration, or for unit testing. However, to test your webhook configuration from end to end, you should always trigger webhooks by performing the related action in Shopify.

Because most webhook deliveries use remote endpoints, you can trigger the command from any directory where you can use Shopify CLI, and send the webhook to any of the supported endpoint types. For example, you can run the command from your app's local directory, but send the webhook to a staging environment endpoint.

To learn more about using webhooks in a Shopify app, refer to Webhooks overview.

• Webhooks triggered using this method always have the same payload, so they can't be used to test scenarios that differ based on the payload contents.
• Webhooks triggered using this method aren't retried when they fail.
• Trigger requests are rate-limited using the Partner API rate limit.
• You can't use this method to validate your API webhook subscriptions.

Lists the available commands and describes what they do.

You can add a help flag to any command to learn more about it. Use --help or -h.

Lists the version of Shopify CLI included in the project.

If nothing is returned from this command, then your project isn't using Shopify CLI 3.0 or higher, and you might need to migrate.

Shopify CLI acts as a dependency of your app. This command upgrades the @shopify/cli and @shopify/app dependencies to their latest versions.