Matt Glaman

Announcement of support as well: https://v8.dev/features/wasm-bigint

Actually this shows Memory64 support: https://webassembly.org/features/. It looks like it's all behind feature flags. I wonder if the `-sWASM_BIGINT` flag would be enough? That has wide spread support.

I tried a build with `-sWASM_BIGINT` and it crashed: `Cannot convert 0 to a BigInt`. ``` 500: Internal Server Error. ================================================================================ Stacktrace: TypeError: Cannot convert 0 to a BigInt at...

Also, even with the flag this test failed: ``` test('PHP_INT_SIZE', async () => { const php = new PhpNode(); let stdOut = '', stdErr = ''; php.addEventListener('output', (event) => event.detail.forEach(line...

`-s MEMORY64` assumes `-sWASM_BIGINT` which was crashing. Maybe this cannot be done quite yet

also needed in `packages/php-cgi-wasm/static.mak`

There is also the overhead where Next.js is running for _all_ pages because it decorates the renderer.

Possible workaround: ```js import { PhpBase } from 'php-wasm/PhpBase.mjs'; import PhpBinary from 'php-wasm/php-node.mjs'; const php = new PhpBase(PhpBinary, { persist: { mountPath: '/persist', localPath: process.cwd() + '/tests/fixtures/' }, sharedLibs: [...

I don't think this is quite working either as when I debug I find it trying to load `php83-zlib.so.so`

WIP branch where I'm trying this out: https://github.com/mglaman/wasm-drupal/blob/9768d93d0b4bca056a87d40dfc5a06264b2c5190/tests/init-phpcode.test.js ``` Warning: PHP Startup: Invalid library (maybe not a PHP library) 'libzip.so' in Unknown on line 0 Warning: PHP Startup: Unable to...