Doesn't work on everyone but Daniel's computer

[danielbachhuber]

Props to @dmsnell for finding the cause:

[danielbachhuber]

@adamziel @dmsnell I'm not sure why it's getting packed up like this 🙃

Here's where I'm pulling in getPHPLoaderModule:

wordpress-playground-vscode/src/extension.ts

Line 9 in e78d5ac

import { PHP, PHPServer, loadPHPRuntime, getPHPLoaderModule, PHPBrowser } from './built-php-wasm-node';

There aren't any symlinks that I'm aware of in the project. All I did was run vsce package.

Any ideas?

[dmsnell]

@adamziel suggested this fix to the webpack config, presuming that it was realizing the full filepaths at compile time when it should have left them hanging.

Copy the contents and run pbpaste | patch -p1

diff --git a/webpack.config.js b/webpack.config.js
index 7febf52..1228ffc 100644
--- a/webpack.config.js
+++ b/webpack.config.js
@@ -30,6 +30,9 @@ const extensionConfig = {
     extensions: ['.tsx', '.ts', '.js']
   },
   module: {
+    parser: {
+      javascript: { importMeta: false }
+    },
     rules: [
       {
         test: /\.ts$/,

[adamziel]

Webpack replacing import.meta.url in built-php-node-wasm with a literal path. If the config @dmsnell posted works, great. If not, I've been using (import.meta || {}).url as a workaround.

[danielbachhuber]

Just pushed a 0.0.2 with that change applied. Can someone test to see if it works now? 65726e2

@adamziel Can you create an Azure DevOps account so I can grant you publishing rights to the extension? I'm traveling tomorrow, then AFK Friday and next week, so it'd probably be good to remove my bus factor.

[dmsnell]

strangely, after updating to this new version, I get the following error when I attempt to launch the playground