Can't start wp-now on Windows OS because of file path fatal #11

t-hamano · 2023-05-24T04:43:15Z

I have tried wp-now on both Windows host OS and WSL2 and could not start it. Ths may be a problem with my environment, is there anything I should try?

Commands executed

git clone https://github.com/WordPress/twentytwentythree.git
npm install -g @wp-now/wp-now
cd ./twentytwentythree
wp-now start

Occurred Error

ReferenceError: Event is not defined
    at Object.<anonymous> (/home/{username}/.volta/tools/image/packages/@wp-now/wp-now/lib/node_modules/@wp-now/wp-now/node_modules/@php-wasm/node/index.cjs:66566:33)
    at Module._compile (internal/modules/cjs/loader.js:1114:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
    at Module.load (internal/modules/cjs/loader.js:979:32)
    at Function.Module._load (internal/modules/cjs/loader.js:819:12)
    at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:203:29)
    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
    at async Object.loadESM (internal/process/esm_loader.js:68:5)
    at async handleMainPromise (internal/modules/run_main.js:59:12)

Environment

Note: Both environments use Volta as their version control tool.

Windows Host

OS: Windows OS 11
Node Version: 14.21.1

WSL2

OS: Ubuntu 20.04.4 LTS
Node Version: Tested with both 14.21.3 and 16.18.0

The text was updated successfully, but these errors were encountered:

adamziel · 2023-05-24T07:29:32Z

@t-hamano You'll need Node.js 18+, the error message isn't very clear about that unfortunately – I'd love to clarify it.

t-hamano · 2023-05-24T09:50:46Z

@adamziel
Thanks for the info!

I was able to move beyond the error in Windows OS by changing the Node version to 18, but another error occurred.

Error Log

wp-now start
Starting the server......
directory: D:\Desktop\twentytwentythree
mode: theme
php: 8.0
wp: latest
Downloading WordPress latest...
Downloading SQLite...
Error: Could not mount C:\Users\tetsuaki.hamano\.wp-now\mu-plugins: There is no such file or directory OR the parent directory does not exist.
    at descriptor.value (C:\Users\tetsuaki.hamano\AppData\Local\Volta\tools\image\packages\@wp-now\wp-now\node_modules\@wp-now\wp-now\node_modules\@php-wasm\node\index.cjs:67333:17)
    at mountMuPlugins (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:623:7)
    at runPluginOrThemeMode (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:589:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:501:9
    at async applyToInstances (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:437:5)
    at async startWPNow (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:486:3)
    at async startServer (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:707:42)
    at async Object.handler (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:864:25) {
  [cause]: ErrnoError
      at Object.ensureErrnoError (C:\Users\tetsuaki.hamano\AppData\Local\Volta\tools\image\packages\@wp-now\wp-now\node_modules\@wp-now\wp-now\node_modules\@php-wasm\node\index.cjs:20233:33)
      at Object.staticInit (C:\Users\tetsuaki.hamano\AppData\Local\Volta\tools\image\packages\@wp-now\wp-now\node_modules\@wp-now\wp-now\node_modules\@php-wasm\node\index.cjs:20241:10)
      at Object.init3 (C:\Users\tetsuaki.hamano\AppData\Local\Volta\tools\image\packages\@wp-now\wp-now\node_modules\@wp-now\wp-now\node_modules\@php-wasm\node\index.cjs:24083:6)
      at loadPHPRuntime (C:\Users\tetsuaki.hamano\AppData\Local\Volta\tools\image\packages\@wp-now\wp-now\node_modules\@wp-now\wp-now\node_modules\@php-wasm\node\index.cjs:67352:38)
      at doLoad (C:\Users\tetsuaki.hamano\AppData\Local\Volta\tools\image\packages\@wp-now\wp-now\node_modules\@wp-now\wp-now\node_modules\@php-wasm\node\index.cjs:68234:31)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async _NodePHP.load (C:\Users\tetsuaki.hamano\AppData\Local\Volta\tools\image\packages\@wp-now\wp-now\node_modules\@wp-now\wp-now\node_modules\@php-wasm\node\index.cjs:68206:12)
      at async startWPNow (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:460:7)
      at async startServer (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:707:42)
      at async Object.handler (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:864:25) {
    node: undefined,
    setErrno: [Function (anonymous)],
    errno: 44,
    message: 'FS error'
  }
}

The mount path (C:\Users\tetsuaki.hamano\.wp-now\mu-plugins) indicated by this error exists on the host OS. However, compared to the results of the WSL2 run, we noticed that the following directories are missing:

C:\Users\tetsuaki.hamano\.wp-now\wp-content\twentytwentythree-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\mu-plugin
C:\Users\tetsuaki.hamano\.wp-now\wp-content\twentytwentythree-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\database

I still don't understand the project, but if I have time I will try to find the cause.

jason3by2 · 2023-05-24T11:57:52Z

Can confirm I'm getting the exact same error, using node v18.16.0, will report back if I can get past it.

adamziel · 2023-05-24T12:11:11Z

Interesting! Thank you so much for surfacing this issue @t-hamano and helping to triage @jason3by2! This helps with making it work for all the Windows users out there.

Solutions-wise, I wonder if this path is even visible/accessible from Node.js. Could it be a permissions issue? Could that be an issue with mixing file:///C:/ notation and C:\ notation?

cc @danielbachhuber @sejas @wojtekn

t-hamano · 2023-05-24T13:39:14Z

Could that be an issue with mixing file:///C:/ notation and C:\ notation?

The URI with the file: protocol shown in the error log seems to be at least accessible from the browser. Therefore, I believe this notation is correct:

at mountMuPlugins (file:///C:/Users/tetsuaki.hamano/AppData/Local/Volta/tools/image/packages/@wp-now/wp-now/node_modules/@wp-now/wp-now/main.js:623:7)

The location indicated by this error is this line:

https://github.com/WordPress/wordpress-playground/blob/043f677f36528e72108d8d6fa8b4d311ec43bf2d/packages/wp-now/src/wp-now.ts#L296

Perhaps vfsDocumentRoot is not the correct path?

richard-bonk-bf · 2023-05-25T11:07:22Z

@adamziel Thanks for the info!

I was able to move beyond the error in Windows OS by changing the Node version to 18, but another error occurred.

Error Log
The mount path (C:\Users\tetsuaki.hamano\.wp-now\mu-plugins) indicated by this error exists on the host OS. However, compared to the results of the WSL2 run, we noticed that the following directories are missing:

C:\Users\tetsuaki.hamano\.wp-now\wp-content\twentytwentythree-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\mu-plugin

C:\Users\tetsuaki.hamano\.wp-now\wp-content\twentytwentythree-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\database

I still don't understand the project, but if I have time I will try to find the cause.

I am getting the same error.

danielbachhuber · 2023-05-25T14:49:57Z

@t-hamano @richard-bonk-bf @narinder9 I'm unable to reproduce because I don't have a Windows machine, unfortunately. My guess is that it's a path issue. To start on the debugging journey, can you install from Git clone and see if the issue reproduces with nx preview wp-now start ?

t-hamano · 2023-05-25T15:24:07Z

@danielbachhuber

Unfortunately, because that script contains UNIX commands, it cannot be debugged on the Windows host OS. The results of the nx preview wp-now start command are shown in the video below:

6eae1c565760fd778d2d5b898b0bab0c.mp4

If on WSL, that command will work fine, but will instead cause the problems mentioned in this comment. Also, this problem would need to be verified on a Windows host OS, not a WSL.

This is why I submitted WordPress/wordpress-playground#435 😅

danielbachhuber · 2023-05-25T15:28:16Z

@t-hamano I guess this shows how thoroughly we tested on Windows 😅

All of this makes sense, thanks! I guess we'll need to figure out a solution for WordPress/wordpress-playground#435 first.

wojtekn · 2023-06-05T10:51:18Z

I reproduced that issue on Windows 11 with PowerShell:

PS C:\Users\wojtek\playground-tools> wp-now start --path=../wordpress-seo
Starting the server......
directory: ../wordpress-seo
mode: plugin
php: 8.0
wp: latest
Downloading WordPress latest...
Downloading SQLite...
Error: Could not mount C:\Users\wojtek\.wp-now\mu-plugins: There is no such file or directory OR the parent directory does not exist.    at descriptor.value (C:\Users\wojtek\AppData\Roaming\npm\node_modules\@wp-now\wp-now\node_modules\@php-wasm\node\index.cjs:67405:17)
[...]

Then I tried running the development version of the wp-now tool to debug it, but I couldn't run the build on Windows. I reported it under another ticket #66. We must fix the build issue to debug the mounting problem more.

adamziel · 2023-06-06T16:17:57Z

playground-tools/packages/wp-now/src/wp-now.ts

Lines 321 to 326 in 4a0ea12

    
           function mountMuPlugins(php: NodePHP, vfsDocumentRoot: string) { 
        
           	php.mount( 
        
           		path.join(getWpNowPath(), 'mu-plugins'), 
        
           		path.join(vfsDocumentRoot, 'wp-content', 'mu-plugins') 
        
           	); 
        
           }

The first path.join() yields C:\Users\adam\.wp-now\mu-plugins which is fine

The second path.join() yields \var\www\html\wp-content\mu-plugins which is not a valid path in the VFS

So – we can’t use path.join for VFS paths because it uses the Windows-style slashes on Windows.

…71) ## Description Solves #11 `wp-now` mounts mu-plugins like this: ```ts php.mount( path.join(getWpNowPath(), 'mu-plugins'), path.join(vfsDocumentRoot, 'wp-content', 'mu-plugins') ); ``` The first path is the local HOST path, the second path is a VFS path. On Mac and linux, they both use forward slashes. On Windows, the first path can use backslashes, but the VFS path still needs to use forward slashes. Problem is: `path.join()` transforms all slashes to backslashes on Windows, which makes the second path invalid like `\\var\\www\\html`. This commit corrects that. ## Testing Instructions Confirm wp-now and the VS code extension can both be started on Windows. Confirm they didn't break on Mac or linux. --------- Co-authored-by: sejas <antonio@sejas.es>

t-hamano · 2023-06-07T07:52:04Z

I reinstalled the latest wp-now including #71 on my Windows host OS. I was able to boot successfully and would like to close this issue.

Thank you so much!

danielbachhuber · 2023-06-07T10:05:51Z

Thanks for your help tracking it down, @t-hamano !

jason3by2 · 2023-06-08T02:54:18Z

Heyas, just wanted to pop back in here to confirm that the latest version also runs successfully for me on win10.
Nice work all! :)

adamziel mentioned this issue May 24, 2023

Make the minimal Node.js version clear WordPress/wordpress-playground#429

Closed

adamziel added Bug Something isn't working wp-now labels May 24, 2023

danielbachhuber mentioned this issue May 24, 2023

wp-now: Error if node doesn't meet the minimum required version WordPress/wordpress-playground#434

Merged

t-hamano mentioned this issue May 24, 2023

Compatibility with Windows and WSL WordPress/wordpress-playground#435

Open

danielbachhuber mentioned this issue May 25, 2023

404 Error:- 404 File not found while trying to access :- http://127.0.0.1:8881 on windows WordPress/wordpress-playground#432

Closed

danielbachhuber changed the title ~~Can't start wp-now on Windows OS~~ Can't start wp-now on Windows OS because of file path fatal May 25, 2023

danielbachhuber transferred this issue from WordPress/wordpress-playground May 31, 2023

wojtekn self-assigned this Jun 1, 2023

adamziel mentioned this issue Jun 6, 2023

Fix fatal startup crash on windows caused by an invalid mount() path #71

Merged

t-hamano closed this as completed Jun 7, 2023

flexseth mentioned this issue Apr 3, 2024

Known limitations of the Playground adamziel/playground-docs-workflow#34

Closed

1 task

ironnysh mentioned this issue Apr 17, 2024

Documentation for using wp-now with Playground adamziel/playground-docs-workflow#31

Closed

lgersman mentioned this issue Jul 2, 2024

wp-now feature request : run phpunit tests within wp-now #321

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Can't start wp-now on Windows OS because of file path fatal #11

Can't start wp-now on Windows OS because of file path fatal #11

t-hamano commented May 24, 2023

adamziel commented May 24, 2023

t-hamano commented May 24, 2023

jason3by2 commented May 24, 2023

adamziel commented May 24, 2023 •

edited

Loading

t-hamano commented May 24, 2023

richard-bonk-bf commented May 25, 2023

danielbachhuber commented May 25, 2023

t-hamano commented May 25, 2023

danielbachhuber commented May 25, 2023

wojtekn commented Jun 5, 2023

adamziel commented Jun 6, 2023 •

edited

Loading

t-hamano commented Jun 7, 2023

danielbachhuber commented Jun 7, 2023

jason3by2 commented Jun 8, 2023

Can't start wp-now on Windows OS because of file path fatal #11

Can't start wp-now on Windows OS because of file path fatal #11

Comments

t-hamano commented May 24, 2023

Commands executed

Occurred Error

Environment

Windows Host

WSL2

adamziel commented May 24, 2023

t-hamano commented May 24, 2023

jason3by2 commented May 24, 2023

adamziel commented May 24, 2023 • edited Loading

t-hamano commented May 24, 2023

richard-bonk-bf commented May 25, 2023

danielbachhuber commented May 25, 2023

t-hamano commented May 25, 2023

danielbachhuber commented May 25, 2023

wojtekn commented Jun 5, 2023

adamziel commented Jun 6, 2023 • edited Loading

t-hamano commented Jun 7, 2023

danielbachhuber commented Jun 7, 2023

jason3by2 commented Jun 8, 2023

adamziel commented May 24, 2023 •

edited

Loading

adamziel commented Jun 6, 2023 •

edited

Loading