Jon Surrell

> That said, given the module's complexity, if you'd prefer I revert the markdown changes and keep only the copy-post fix, let me know. @copilot Since this appears to be...

I observed this issue when I restored a revision as well with: ```sh wp eval 'wp_restore_post_revision(123);' ``` I thought it might be a Core issue with revisions, but was unable...

Potentially related: https://github.com/Automattic/jetpack/issues/1673

Will you provide some details about the build issues? In particular how should the behavior be verified. Is a successful `npm run build` sufficient? - I understand that the changes...

Will you share some details on the unintended consequences for other packages? Is it breaking some behavior or how does it manifest?

This is a mess 😖 In theory, webpack supports wasm natively by enabling `experiments.asyncWebAssembly`. I also switched from using `conditionNames` (affecting all packages) to patch the `wasm-vips` package. This still...

I've spent some time fighting with this again and I've made progress, but I'm still not happy with it. I'm starting to think the necessary wasm files should just be...

One of the ways this breaks when loading the wasm files as wasm is errors like this: ``` ERROR in ./node_modules/wasm-vips/lib/vips-jxl.wasm Module not found: Error: Can't resolve 'GOT.func' in '…/node_modules/wasm-vips/lib'...

I plan to help sort out the details here, but I'm prioritizing other work I hope to ship in WordPress 6.7. After that work is settled I can dedicate some...

I believe this would fix https://core.trac.wordpress.org/ticket/45387.