Make WordPress Core

Opened 5 years ago

Closed 19 months ago

#48288 closed defect (bug) (invalid)

WordPress Installation - "npm run env:start" not working on windows

Reported by: veminom's profile veminom Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.3
Component: Build/Test Tools Keywords: reporter-feedback close
Focuses: Cc:



npm run env:start

seems to be not working on Windows

Steps to reproduce:

  1. Open windows environment.
  2. Clone WP Trunk -
    git clone git:// wp-trunk
  3. Navigate to cloned directory -
    cd wp-trunk
  4. Install npm for the project -
    npm install
  5. Got an error for PhantomJS -
    PhantomJS not found on PATH
    Saving to C:\Users\PREMAN~1\AppData\Local\Temp\phantomjs\
    Error making request.
    Error: getaddrinfo ENOTFOUND
        at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:57:26)


  1. Installed PhantomJS using NPM -
    npm install phantomjs-prebuilt
  2. Ran
    npm install
    again and it working without any errors
  1. Ran
    npm run env:start

Command but it failed with the following errors:

'docker-compose' is not recognized as an internal or external command,
operable program or batch file.
    throw err;


There are 2 points I'm concerned with

  1. PhantomJS should get installed as a dependency while running
    npm install
  1. The errors I'm getting while running
    npm run env:start

Change History (6)

This ticket was mentioned in Slack in #core by veminom. View the logs.

5 years ago

#2 @johnbillion
5 years ago

  • Milestone changed from Awaiting Review to Future Release

#3 @bookdude13
4 years ago

Hey @veminom! I just started doing some dev with WP, and also use Windows. Have you installed Docker, as mentioned in in the repo and in

#4 @desrosj
4 years ago

  • Keywords reporter-feedback added; needs-patch removed

Hi @veminom!

Are you still experiencing this issue? I can't be certain, but the error message you shared seems to be a problem with NPM downloading the PhantomJS package. The second message seems to indicate Docker is not installed or available.

Can you please confirm that Docker was installed and running when you ran those commands? Also, I did find some StackOverflow posts that indicated some users needed to restart Docker after installing in order for it to work properly.

#5 @bgoewert
19 months ago

  • Keywords close added

Docker Desktop does not ship with the old docker-compose.

'docker-compose' is not recognized as an internal or external command,
operable program or batch file.

If this still happens for you, ensure that Docker Compose V1/V2 compatibility mode is enabled. This creates an "alias" for the new docker compose. See

Image showing what this looks like in the Docker Desktop General Settings. Note that this image was taken on a Linux machine, but the same thing applies to Windows.

#6 @JeffPaul
19 months ago

  • Milestone Future Release deleted
  • Resolution set to invalid
  • Status changed from new to closed

Thanks @bgoewert, closing for now.

Note: See TracTickets for help on using tickets.