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

[veminom]

Command

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://develop.git.wordpress.org/ 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
   Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-windows.zip
   Saving to C:\Users\PREMAN~1\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip
   Receiving...
   
   Error making request.
   Error: getaddrinfo ENOTFOUND github-production-release-asset-2e65be.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com:443
       at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:57:26)
   

Screenshot: ​https://cl.ly/4f89e35a9128

6. Installed PhantomJS using NPM -

   npm install phantomjs-prebuilt
   

7. Ran

   npm install
   

   again and it working without any errors

8. 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.
child_process.js:662
    throw err;

Screenshot: ​https://cl.ly/08c56b836dce

There are 2 points I'm concerned with

1. PhantomJS should get installed as a dependency while running

   npm install
   

2. The errors I'm getting while running

   npm run env:start
   

[bookdude13]

Hey @veminom! I just started doing some dev with WP, and also use Windows. Have you installed Docker, as mentioned in README.md in the repo and in ​https://make.wordpress.org/core/2019/08/05/wordpress-local-environment/?

[desrosj]

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.

[bgoewert]

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 ​https://www.docker.com/blog/announcing-compose-v2-general-availability/

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.

[JeffPaul]

Thanks @bgoewert, closing for now.