Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 55 ยท Orientation

Tooling and Setup

Set up your machine for Shopify app development: Node.js, Git, the Shopify CLI, a developer account, a development store and shopify auth login, step by step.

A good setup saves hours. Most of the "my app will not start" problems beginners meet come from an old Node version, a missing Git, a CLI that is out of date, or being signed in to the wrong account. This lesson walks through the pieces in the order you need them, tells you how to check each one, and ends with a script that tests an environment report against the requirements.

Everything on the command line below is real and read-only here: this site cannot install software on your computer. The runnable part is a stand-in that checks a description of your environment, which is a handy pattern for your own onboarding scripts too.

What you need

Piece Why How to check
Node.js (a current LTS release) Runs the CLI and the template node --version
A package manager (npm comes with Node) Installs dependencies npm --version
Git The CLI and template use it git --version
Shopify CLI Creates, runs and deploys apps shopify version
A developer account Owns your apps sign in at the Shopify developer site
A development store Where your app runs listed in your dashboard
An editor and a browser Where you work any

Node.js and Git

Install Node.js from the official site or a version manager such as nvm, fnm or Volta. The Shopify CLI and the React Router template require a reasonably recent Node. The exact minimum moves over time (the template declares it in the engines field of its package.json), so install the current LTS and read that field when in doubt. Using a version manager helps because different projects ask for different Node versions.

Git comes from git-scm.com or your system package manager. The CLI uses it when it clones the template, and you will want it for your own history anyway.

The Shopify CLI

The CLI is an npm package. Installing it globally keeps the shopify command available everywhere:

Terminal
npm install -g @shopify/cli@latest
shopify version

Inside an app created from the template the CLI is also a project dependency, so a team can pin one version for everyone. When you read an error on Windows about scripts being disabled, that is PowerShell's execution policy, not Shopify; running the command from a different terminal or adjusting the policy for your user fixes it.

Update the CLI often. Commands and flags change, and the template expects a recent CLI. npm install -g @shopify/cli@latest is the whole upgrade.

Accounts and stores

  1. Create a developer account. This account owns your apps and development stores. Use an email you control long term; a shared team inbox is a good choice for company work.
  2. Create a development store. From the dashboard, add a store and choose to populate it with test data. Pick a memorable name, because the CLI will ask for the store URL (something.myshopify.com) often.
  3. Sign in from the CLI. The CLI opens a browser window to authorize your account:
Terminal
shopify auth login

The login stores credentials on your machine so later commands (shopify app dev, shopify app deploy) can act as you. shopify auth logout removes them. If the CLI seems to talk to the wrong organization or store, log out and in again, and check which account is active in the browser window it opens.

flowchart LR
    N["Node.js and npm"] --> C["Shopify CLI"]
    G["Git"] --> C
    D["Developer account"] --> L["shopify auth login"]
    C --> L
    L --> S["Development store"]
    S --> R["Ready to create an app"]

The CLI needs Node and Git; commands that touch Shopify need you signed in.

Versions you will meet

Several things carry a version, and mixing them up is a classic source of confusion:

  • Node.js and npm: your runtime.
  • Shopify CLI: the tool. It has its own version number.
  • The template: a Git repository. Newer templates can change file layout.
  • The API version: a date such as 2026-10. Shopify publishes a stable API version every quarter and supports each for about a year. Your configuration and your API calls name one. API Versioning and Deprecations covers it.
  • Library packages: the Shopify app package for your framework, with its own release cycle.

When you ask for help, give all five.

Useful commands to know early

These are read-only here; you will run them in the next lesson.

Terminal
shopify app init          # create a new app from a template
shopify app dev           # run it locally with a tunnel
shopify app deploy        # create a new app version on Shopify
shopify app info          # show app and environment information
shopify app generate extension   # add an extension
shopify auth logout       # forget the current login
shopify help              # list commands

shopify app info is especially handy: it prints the CLI version, Node version and app settings, which you can paste into a support request. Check shopify help for the exact commands in your CLI version, since command names are occasionally adjusted.

A runnable environment checker

You can use the same idea for your own team. The script below takes a report (a plain object, as if collected from the terminal) and checks it against requirements. The report is fake, and the minimum versions are examples for the demo; in real life you would read them from your template's package.json. Edit the report and run it again to see the messages change.

JS Check an environment report

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The comparison is done part by part, number by number, because comparing version strings as text is a bug (as text, "3.9" is greater than "3.10").

A second stand-in: the setup order

New teammates often run commands in the wrong order. The next script models the dependency chain from the diagram and tells you what to do next, given what is already done.

JS What should I do next?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Steps that can happen in the same round do not depend on each other, so you can do them in any order.

Troubleshooting checklist

  • shopify: command not found: the npm global folder is not on your PATH, or the install failed. Run npm config get prefix and check that its bin folder is on the PATH.
  • The template fails to install: check the Node version against the template's engines field.
  • The CLI asks you to sign in again and again: log out, close the browser tab it opens, and log in once more.
  • You see a store you did not expect: run shopify auth logout, then log in with the intended account.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which command signs the CLI in to your developer account?

    shopify auth login opens the browser to authorize your account. Other commands use that stored login.
  2. 2. Why compare version numbers part by part instead of as text?

    Text comparison orders character by character, so "3.9" looks bigger than "3.10". Compare each numeric part.
  3. 3. Where can you find the Node versions a template supports?

    The template declares the supported Node range in package.json, and that is the most reliable source.
  4. 4. What is a development store used for?

    Development stores are free test stores where your app is installed while you build.

Summary

  • You need a current Node LTS, Git, the Shopify CLI, a developer account and a development store.
  • Install the CLI with npm install -g @shopify/cli@latest and sign in with shopify auth login.
  • Keep track of five versions: Node, CLI, template, API version and library packages.
  • shopify app info collects details useful for support requests.
  • The environment checker and planner here are stand-ins for the habit of scripting your setup; the commands are real but read-only on this site.

Next: Creating an App with the CLI