Npm run dev error

Topic summary

Issue: Running “npm run dev” for a Shopify app hangs after choosing a store, then shows an empty error dialog. It previously worked without issues.

Attempts so far: Cleared npm cache, deleted node_modules/package.json, reinstalled dependencies (npm install), and even recreated the app. npm-cache logs provided no useful clues. A screenshot of the empty error dialog is attached and relevant.

Environment details: Another user reproduced the issue on Shopify CLI 3.49.3, Node 18.16.0, npm 9.5.1.

Suggestions/requests from replies:

  • Update Shopify CLI to the latest version.
  • Specify operating system (Mac or Windows).
  • Re-run the command with the --verbose flag and share the output for diagnosis.

Status: Unresolved/ongoing. Key next steps are to confirm OS and CLI version, run with --verbose, and provide the detailed logs to identify the cause.

Notes: npm = Node package manager command; Shopify CLI = Shopify’s command-line interface.

Summarized with AI on January 10. AI used: gpt-5.

Whenever I attempt to run the npm run dev command I get stuck after asking which store I would like to use to view my project in and with the info box showing underneath. After maybe 10-15 seconds of waiting, an empty error box appears.

I didn’t have any issues a few months ago and I have tried many basic fixes such as clearing cache, deleting node modules / package.json and running npm install again, and recreating my app from scratch.

My npm-cache logs don’t give any meaningful information either.

JonThoms327_0-1695143761915.png

Hi JonThoms327,

Have you tried updating the Shopify CLI to the most recent version?

I am getting the same error. I am using Shopify CLI latest version 3.49.3, Node 18.16.0 and npm 9.5.1.

Hi, @Priyanka_1 did you solve this issue? If so can you guide me I’m also having same issue with my app.

Pudiste resolverlo?

Hello [email removed]JonThoms327

please do you solve this i have the same issues on my app.

Are you running the CLI on Mac or Windows?

Also if you could run the command with the --verbose flag and share the output, we can get a better view of what might be causing this.